Simona Oancea
Software Engineer. Architecture nerd.
Bucharest, Romania
Actions
I've spent the last decade building backend systems in Java — some that needed to handle millions of requests, others that probably should have been retired years ago. I've seen what works at scale and what falls apart when nobody plans for what comes next. I enjoy sharing what I've learned along the way. I care most about the architecture decisions that seem small today, but define your system's future.
Area of Expertise
Topics
The Architecture Decision You Can Undo: Microservice Boundaries with Spring Modulith
We've spent a decade telling developers that microservices are the grown-up way to build software. That real engineers decompose everything into independently deployable services from day one. And we've spent that same decade dealing with the fallout. Distributed debugging. Eventual consistency headaches. Integration tests held together by prayer. And teams that can't ship a feature without a cross-team deployment ceremony.
What if the whole premise was wrong? Not microservices themselves, but the timing. What if the right number of services at the start of a project is one?
Using Spring Modulith, I'll show you a monolith with boundaries that most microservice architectures would envy. Enforced by tests, not by network latency. Modules that can be extracted when the pain is real and put back when it isn't. This isn't a talk about choosing the right architecture. It's a talk about building one that lets you change your mind.
Because the decisions that matter most are the ones you can undo.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top