"Hey, Olimpiu. My name is Marcin Grzejszczak. I've been working on the Spring and Micrometer open-source teams for the past decade, mainly focusing on the topic of contract tests, so Spring Cloud Contract, continuous delivery deployment, and Spring Cloud Sleuth. So, distributed tracing. And recently, for the last couple of years, Micrometer, Micrometer Observation and Micrometer Tracing mainly."
"We started with a monolith, criticising its ugliness. And then we realised that at points, monoliths are good, and at other points, microservices are good. But what's necessary is always to know what's happening under the hood. If it doesn't work in a monolith, it will be worse in a microservices setup"
"Yes, absolutely. And recently, I started doing mentoring sessions. In one of the sessions I had, somebody said that they're planning their career and they don't know what to pick. And they said, 'Yes, maybe microservices are the way to go'. And I'm like, 'If you can't write proper code in a monolithic app, you'll make it even worse than a distributed one'. So, I am absolutely not surprised that with the emergence of the trend for microservices, people fault that certain principles do not matter. It's quite the opposite. It's always the principles that matter. And if we do not know those, then if we're going to distribute it, computing distributed systems, we'll make it far worse over there."
Work on Spring and Micrometer open-source projects spans a decade with focus on contract tests, Spring Cloud Contract, continuous delivery deployment, Spring Cloud Sleuth, distributed tracing, Micrometer Observation, and Micrometer Tracing. Monolithic applications can be appropriate in many situations while microservices suit other cases. Fundamental coding skills and software principles remain essential regardless of architecture. Poor design and code in a monolith become worse in distributed systems. Choosing microservices for career or trend reasons without mastering core practices risks degrading system quality and maintainability.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]