Breaking Ground in Microservices

Real stories from teams building distributed systems that actually work. We're tracking what matters in architecture, deployment strategies, and the everyday challenges developers face when services multiply.

Recent Insights

What we're learning from real implementations across different team sizes and business contexts

Development team collaborating on distributed system architecture
Deployment

Rolling Back Without Panic

February 28, 2025

A fintech team in Taipei rolled back 14 services last month after a database migration went sideways. Their post-mortem revealed something interesting about versioning strategies that we hadn't considered before.

Technical infrastructure showing system monitoring and performance metrics
Monitoring

Observability That Developers Use

February 15, 2025

Spent two weeks with a team that actually enjoys debugging production issues. Their secret? They built monitoring dashboards that answer questions instead of just displaying data. The difference is subtle but massive.

Architecture

Event-Driven Until It Isn't

January 30, 2025

Event sourcing feels elegant until you need to query historical data across multiple aggregates. A logistics company found this out during their Q4 reporting cycle. Their workaround became their new standard approach, and it's worth examining why.

Linnea Westerlund, Systems Architect

Linnea Westerlund

Systems Architect

Vesna Petrović, Platform Engineer

Vesna Petrović

Platform Engineer

What We're Seeing in 2025

The conversation shifted from 'should we break this monolith' to 'which parts deserve their own lifecycle.' That's progress. Teams are getting pragmatic about when distributed complexity pays off.

Linnea and Vesna work with development teams across Taiwan's startup ecosystem. They've noticed something interesting this year — fewer teams are starting with microservices, but the ones that do transition have much clearer reasons.

Last autumn, they ran a workshop series in Taichung where teams mapped their actual deployment patterns against their ideal architecture. The gap analysis revealed that most bottlenecks weren't technical at all. Communication patterns between teams mattered more than the technology stack.

Explore Learning Resources