When faced with a challenging legacy code base, tightly coupled and void of discernible structure: a big ball of mud, it is common to decide to refactor this monolith to a microservice architecture to separate concerns and split the codebase up, however without any clear boundaries you are in danger of creating a distributed big ball of mud.

You may recognise the symptoms of a distributed ball of mud: a large unfocused 'common' library shared between multiple services; performance issues as your front end makes calls to multiple back end API's to serve a single request; dependency hell on deployments as you have to release multiple code bases simultaneously and uptime issues as a single microservice going down brings down your entire application.

In this talk I'm going to cover some of the common pitfalls you might encounter when building a microservice architecture and show you how to use an event driven architecture to build truly scalable microservices


Comments are closed.

Very good

Very nice talk about microservices and their pitfalls, learned a lot

Great talk about real world microservices, with clear and properly worked out examples of what can go wrong with applying this architecture, including what you can do about it. Fun examples too!

Feedback: The speaker references specific tools / methods / projects to solve problems, but they are not displayed on the slide. That might be a missed opportunity if it's not intentional.

Remco Brink at 13:16 on 8 Jun 2018

Informative, but could've gone a bit more in-depth with practical examples

Good stuff!

Very helpful by sharing his experience on the subject. And he was objective by given pros and cons.

Good talk. Keep doing it!

f4br1cat0r at 18:26 on 10 Jun 2018

Loved the pros and cons. Might have benefited from a little more examples

The description says it, it gives a lot of information with scenarios and issues that arise and also gave solid advice on how you could solve those issues.

Good informative talk, although the presentation bit might be worked on a bit. Doing it more often will probably help. Putting a bit less on a slide and showing more slides might also help making the talk a bit more dynamic and feel more "alive".
Also try to include things you reference to on your slides, even if only as a small note on the bottom.

I already used the suggestion "don't make it a nano-service" the monday after the conference.

Good talk :)

Nic Wortel at 00:06 on 13 Jun 2018

Not just a great introduction for people who want to start working with microservices, but also (and maybe especially) helpful for those that are already working with them and are experiencing some of the drawbacks listed in the presentation. I really liked how you not just listed the risks/drawbacks of a microservice architecture but also provided the audience with practical advice on how to solve/prevent them.

I do believe that you would be even more successful in delivering your message if you find a way to present the content in a bit more "lively" way. Especially for people new to the subject it might be a bit dry and hard to follow.

Nevertheless, a great talk!