Voxxed Days Microservices: David Schmitz on Tips for Failing at Microservices
Software architect and developer David Schmitz introduces his talk on ways to fail at microservices, when this architecture is appropriate, and more ahead of Voxxed Days.
Join the DZone community and get the full member experience.Join For Free
Hi David, tell us who you are and what lead you into microservices.
I am a Principal Architect working for Senacor Technologies, a German consultancy. If this sounds like Powerpoint and Excel, well, in that case, think of me as a regular software developer.
Microservices were practically unavoidable during the last couple of years. First — as always, in our industry — presented as the solution to all our problems, and as reality came back into the discussion, as something that may involve certain tradeoffs. Especially if you leave Greenfield-projects and Hello World-projects behind you.
Ah, and I am a father of three and a total football nut!
What will you be talking about at Voxxed Days Microservices?
As developers (and architects), we tend to jump unto the latest bandwagon. This talk is about anti-patterns and tradeoffs that we encountered in various rather large projects within the financial and insurance industry.
I don't believe that what I am talking about is terribly innovative or new, but rather well known. Nevertheless, we sometimes ignore lessons learned and keep burning ourselves time and time again.
I try to look at the errors we keep repeating and hope that we all have a couple of laughs while doing so.
So, obviously, with such a talk, you came across different problems introduced by microservice architecture. Would you still encourage companies to migrate to that path or to be careful and migrate only if needed?
For me, architecture is mostly answering the question, "How do I want people to communicate when working together?" I was approached by a fellow coder who thought I was discouraging the use of microservices. To be clear: I am not! As with every tool, we just need to be aware of the tradeoffs.
To cut it short: if you are working in an agile software delivery process, then my first instinct would be that microservices could be a good fit.
Basically, it depends. Maybe I should come up with a talk, "Microservices are hard, but so is your monolith." There are no easy answers.
Good, see you soon then.
Beware naive advice. Beware silver bullets. Always keep in mind that success stories always come with an untold story... something like "we needed 5 years of hard work to get where we are."
Voxxed Days Microservices & DZone, Partnering Up
DZoners! Visit Voxxed Days Microservices here to check out ticket info for the show, and use the DZone reader exclusive code: VXDMS_DZONE to get 20% off for the conference and workshop. Grab those tickets while you can, be sure to say hey to our Zone Leaders—Thomas Jardinet and Chris Ward—if you run into them at the show, and enjoy Paris!
Published at DZone with permission of Antonio Goncalves, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.