It is not 2014, but this talk is about Monolith vs. Microservices
All the monolith vs. microservices literature summarizes both approaches’ pros and cons. However, they frequently omit what factors are more decisive in choosing the best architecture for your project.
My years of experience in the Scala industry have shown me that an incorrect granularity of the domain models, an inappropriate communication protocol between microservices, an inefficient serialization strategy, poor observability levels, or improper dependency management are just a few examples of bad decisions that can convert your sophisticated architecture of microservices into a pain. In the end, microservices are not the solution per se; only well-done microservices could be the right solution, and the purpose of this talk is to bring up what aspects make your architecture the best possible.
Why will this talk differ from others dealing with the same topic? Because I will do it with the Scala perspective at all times, according to the native capabilities of the language, the existing libraries, frameworks, and build tools.
Director of Engineering @47deg
I’m not superstitious about monoliths, but just a little stitious about the non-scalable ones.
Join our conference
Subscribe and follow @ScalaDays on Twitter for the latest conference updates.