15 entries tagged "software architecture" — 10 posts, 5 links.
This is a durable architecture reference because it gives teams a simple way to choose the right level of diagram: context, containers, components, and code. Good diagrams reduce argument cost.
It fits the product-minded architecture thread on the site: architecture is not only what exists, it is what the team can explain, review, and change together.
This older workflow/state-machine link is worth keeping because the lesson keeps repeating: protocols, product flows, and background jobs become easier to reason about when states and transitions are explicit.
It is not modern tooling guidance. It is a useful reminder that workflows are a modeling technique before they are a SaaS category.
This is a useful architecture link because CQRS is powerful and easy to overapply. Separating reads from writes can clarify a system, but it can also introduce synchronization, consistency, and mental overhead.
The value here is the warning label as much as the pattern. Architecture patterns should earn their complexity.
This belongs in the queue because "event-driven" can mean several different things, and teams get into trouble when they use the same phrase for different architectures.
It is especially useful for product and data systems where event notification, event-carried state transfer, sourcing, and stream processing all imply different failure modes.
This is a broad reference, but it is still worth keeping because system design vocabulary helps developers talk across product, infrastructure, and data boundaries.
The caveat is that primers can encourage interview-shaped thinking. Use it to build a map, then ground decisions in the actual product constraints.