🧑💻 Modelling vs diagramming software architecture
📐 Modelling
Modelling is best for long-term system design docs and requires some setup work. Reusable objects and relationships are stored in the model, which keeps all your diagrams up to date.
🧵 1/2
EventCatalog is an open-source project created by @boyney123 for documenting events in event-driven architectures. It provides a markdown-style syntax that can be checked into source control and a UI to visualize events and dependencies.
It has three key concepts.
🧵 1/4
System Design Interview by @alexxubyte and Sahn Lam
📕 Book: amazon.com/dp/1736049119
This popular book covers 13 system design questions and goes into detail with real-world examples and proposed solutions.
Risk storming is a technique created by @simonbrown for collaboratively identifying and assessing risks for your software systems.
You can run a risk-storming workshop with your team in four steps.
🧵 1/3
Customers do know what they want. They're just usually bad at communicating it. A great product manager can discover the truth by asking the right questions.
The Road To Event-Driven Architecture At LEGO.com@sheenbrisals discusses the mechanics of event-driven computing and explains why the engineering team at LEGO.com adopted an event-driven architecture.
📺 youtube.com/watch?v=_g6DA9…
🚀 IcePanel v56: Diagram thumbnail previews on the diagrams list
🔗 u.icepanel.io/51e34d49
🔑 Key product updates
1️⃣ Diagram thumbnail previews
2️⃣ Expand diagram groups in the diagrams list
3️⃣ Forwards button for stepping through history
#softwarearchitecture#c4model
