| Summary: | One of the most difficult tasks an architect will face is untangling the various forces and trade-offs at play in their architectures--and that's particularly true for distributed systems. If an architect thinks they've discovered something that isn't a trade-off, more likely they just haven't identified what the trade-off is yet. After all, as the first law of software architecture states: Everything in software architecture is a trade-off. While the scope of software architecture is almost impossibly broad, unifying elements do exist. But to truly understand and evaluate the significance of trade-offs in architecture, developers need a working knowledge of basic concepts and terminology concerning components, modularity, coupling, and connascence. These expert-led sessions will level up your skills and help you work through the complexity and trade-offs in your own system.
|
|---|
