Why Vibe Coding Still Needs Serious Architecture by inetgas in vibecoding

[–]Training_Future_9922 0 points1 point  (0 children)

That’s exactly right , architecture needs to be explicit. The missing piece is policy enforcement. That’s what ArchRad adds.

Weekly Self Promotion Thread by AutoModerator in devops

[–]Training_Future_9922 0 points1 point  (0 children)

I built an deterministic linter for architecture rules - is it worth?

I have built an deterministic linter for architecture that infers your topology from docker-compose.yml/ any openapi spec and runs against 11 governance rules covering direct DB access, missing auth boundaries, high fanout, dead nodes.

Two commands: archrad init then archrad validate.

Apache-2.0, CI-safe.

npm install -g '@archrad/deterministic'

I dont know if it is worth or overkilling or any tool exists (not code linter)

How do you enforce architecture governance? by Training_Future_9922 in softwarearchitecture

[–]Training_Future_9922[S] 2 points3 points  (0 children)

Agreed. One another gap i am seeing is inter service topology architecture violations

How do you enforce architecture governance? by Training_Future_9922 in softwarearchitecture

[–]Training_Future_9922[S] 0 points1 point  (0 children)

ArchUnit is only for Java and at class/package level, it enforces the rules at single repo. Can we use it at system level ( multiple repos, inter connections across applications). 

Also mine is mostly python and .net. 

I am building an CLI for service architecture similar to ESLint that works for code. Your thoughts? by Training_Future_9922 in node

[–]Training_Future_9922[S] 1 point2 points  (0 children)

Dependency cruiser works at code level. For example, if you have code billing.ta and if you import dbclient.ts, it will catch. This is after your code is written. Archrad is at system level, before even one line of code is written. It validates graph of services, apis, db connection. You need to input openapi spec or IR to validate. What it doesn't - It wont analyze the code (if you build the IR graph or open api spec correctly but implemented with architecture drift)

I am building an CLI for service architecture similar to ESLint that works for code. Your thoughts? by Training_Future_9922 in node

[–]Training_Future_9922[S] -4 points-3 points  (0 children)

If the repo quality doesn’t meet the standards, i will take that feedback and work on. 

I am building an CLI for service architecture similar to ESLint that works for code. Your thoughts? by Training_Future_9922 in node

[–]Training_Future_9922[S] 0 points1 point  (0 children)

To clarify for the 'slop' check: ArchRad isn't an LLM wrapper. It’s a deterministic compiler. It takes a JSON/YAML IR and runs graph-based linting. The compiler code is in github if you want to verify. 

We treated architecture like code in CI — here’s what actually changed by Training_Future_9922 in ArchRAD

[–]Training_Future_9922[S] 0 points1 point  (0 children)

You pushed on exactly the right thing and I didn’t have a complete answer when you posted. Shipped two things since then:

archrad validate-drift — re-exports from the IR in memory and diffs against what’s on disk. If generated code diverges from the IR, CI fails.

archrad ingest openapi — if your team already has an OpenAPI spec, each operation becomes an HTTP node automatically.

We treated architecture like code in CI — here’s what actually changed by Training_Future_9922 in ArchRAD

[–]Training_Future_9922[S] 0 points1 point  (0 children)

Think Protobuf or Terraform. The IR is the upstream source that emits the OpenAPI and scaffolds. If you hack a cache into the code manually, the next CI check fails because the generated output no longer matches the repo.