Designing Microservices and Monoliths with 4+1 Architectural Views

Join waitlist?

4 on waitlist


Every 4th Tuesday of the month

Location visible to members


==== The 4 + 1 Architectural Views: a Practical Guide ====
Christopher Simon (@ChrisSimonAu)

Have you ever worked on a microservices system experiencing these sorts of challenges?

* I’ve separated my system into loosely coupled microservices - why is integration between them still so hard? I’m spending all my time implementing circuit breakers, bulkheads & retry patterns when I’d rather be writing business logic!

* My autonomous microservices teams are still blocking each other from delivery - why?

* We still struggle with version incompatibilities between microservices… we’ve had to invest heavily in consumer driven contract testing to ensure we don’t break things

* Making an update is so hard - we have to update code in multiple repositories containing our shared libraries and wait for a nuget or npm publish cycle in each of them before we can test the integration of changes

Or perhaps you’re a startup who doesn’t want to over-engineer their MVP launch solution, but also doesn’t want to end up with a big ball of mud, or unable to scale their system when the business starts doing well?

The 4+1 architectural views may help. It's an old idea with new promise, providing a powerful explanatory framework for understanding any system that is particularly useful in the modern world of highly distributed systems. Considering each view independently helps reveal the underlying tensions between service decomposition decisions, and the teams that design, build & operate those services,

This talk provides an beginners introduction to the 4+1 views, including how to think about coupling and cohesion & scalability in each view. We'll review code samples of how design decisions play out in the developer experience, and real-life lessons learned applying the views in systems that have scaled to national operations.

Speaker bio:

Chris is the founding CTO of InLoop ( but prefers to spend more time coding than CTO-ing. InLoop provides, a school transaction platform helping hundreds of thousands of Australian parents connect with their school communities, and, a Fintech startup dedicated to tackling payments challenges in the consumer directed care sector, particularly the NDIS and other public insurance schemes.

NOTE: The group meets in the Sydney CBD, near Wynyard station, not in Revesby (there's been some map bugs around this)!
Address for copy paste: level 10/50 Carrington St, Sydney NSW 2000
Google maps link: