#Software-Architecture
44 notas · última:
Moving to Microservices at SoundCloud with Lukasz Plotnicki
An episode of Software Engineering Daily where Lukasz Plotnicki discusses SoundCloud’s move from a monolith to microservices, the technical debt it created, and the lessons learned about architecture.
MonolithFirst
The page argues for starting new applications as a monolith, since microservices add overhead, depend on stable boundaries, and are easier to adopt later after the system’s shape becomes clearer.
Architecture is abstract until operationalized
The post argues that software architecture is only a snapshot until it is implemented, upgraded, monitored, and able to survive real operational conditions. DevOps, continuous delivery, and microservices make those concerns part of design.
My Answers for Microservices Awkward Questions
The author frames his microservices experience as a report about reducing accidental coupling, then answers questions about deployment, ownership, monitoring, tracing, and what counts as a production-ready service.