Writing1 min read

Architecture Notes

Architecture Workshops That Decide

One workshop ended in opinions. The next ended with an owner.

One workshop ended in opinions. The next ended with an owner.

The first session debated microservices versus monolith for two hours. No artifact. The second started with a decision question and finished with names on follow-ups.


Bus versus direct HTTP

The team was stuck on event bus versus direct calls. Delivery needed a call within the week.


Opinions without an owner

We confused exploration with decision. Constraints were missing from the room. People argued from different assumptions.


Outcome before the room fills

Define the outcome before people arrive. Bring real constraints: timeline, ops cost, team size.

Capture decisions live. End with one next step and one owner.


One-page workshop output

Workshop output
Page structure
Problem: cross-service notifications
Options: bus vs direct HTTP (pros/cons)
Decision: direct HTTP for v1; bus in Q2
Owner: Alex; ADR #18 by Friday

Leave with one next step

Leave with one next step, not applause. A workshop is useful when behavior changes the next day.


References