menu

Mono, Micro, Mesco

BackerLeader ●17 ●114 ●232
calendar_today • schedule1 min read

Tony Kelly hosts our latest episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton.

Your system's architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a sticky mess. This episode looks at whether choosing a monolith or microservices fundamentally changes the crucial properties of your architecture.

  • The many factors influencing architecture
  • How team design is part of architecture
  • How to choose between monoliths and microservices
  • The true measure of successful architecture
Part 6 of 14 in CD Office Hours
← Part 5: Branching StrategiesPart 7: Delivering Database Changes →
🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.
Join CoderLegion

More Posts

Delivering Database Changes

Steve Fentonverified - Jul 22

Continuous Delivery Office Hours Ep.4: Mono, micro, mesco

Steve Fentonverified - Jul 27

Modernizing Legacy Software

Steve Fentonverified - Aug 26

The Compliance Ratchet

Steve Fentonverified - Aug 19

Modern Multi-Tenancy

Steve Fentonverified - Aug 5
chevron_left
Steve Fentonverified
15.1k Points • 363 Badges
UK • stevefenton.co.uk
100Posts
151Comments
81Connections
Steve Fenton is an Octonaut at Octopus Deploy. He’s a Software Punk, author, programming-architect, ... Show more

More From Steve Fentonverified

Continuous Delivery Office Hours EP.12. The platform adoption shock

The difference between a millrace and a waterfall

Continuous Delivery Office Hours Ep.6: Change approvals

Related Jobs

View all jobs →

Commenters (This Week)

5 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!