menu

Mono, Micro, Mesco

BackerLeader ●18 ●139 ●261
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 4 of 14 in CD Office Hours
← Part 3: Branching StrategiesPart 5: 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

Stop Treating EDA as Just Pub/Sub. Here’s How to Handle Request/Reply

Stephen - Oct 13

Modernizing Legacy Software

Steve Fentonverified - Aug 26

The Compliance Ratchet

Steve Fentonverified - Aug 19
chevron_left
Steve Fentonverified
16.6k Points • 418 Badges
UK • stevefenton.co.uk
109Posts
172Comments
119Connections
Steve Fenton is an Octonaut at Octopus Deploy. He’s a Software Punk, author, programming-architect, ... Show more

More From Steve Fentonverified

AI Hasn’t Shifted The Bottleneck From Coding To Code Review

Continuous Delivery Office Hours Ep.7: Modern multi-tenancy

Raising the bar on software delivery

Related Jobs

View all jobs →

Commenters (This Week)

4 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!