Let’s have some fun while we entertain the idea that maybe - just maybe! - a microservice architecture would be a great fit for our (next) project. After all, we're almost past the microservices hype. It's time to prove that this can work!

Starting from the premise that a microservice architecture is only viable if we focus not only on the speed of change, but also improve the safety of change, we can learn a lot from the early adopters who have already scouted large parts of the unknown territory before us. Tools and platforms are maturing pretty fast too, so it’s safe to assume that we are now (almost) past the peak of impediments. Let’s start enjoying those microservices!


Comments are closed.

Herberto Graca at 13:21 on 1 Jul 2017

Usually Mathias gives worthy talks but this time i was disapointed. I was expecting much more technical content. The ideas explained were not very deep, we can easily grasp them by reading a few articles.The conference ticket should be worth more.
It also saddens me to say that it sounded a bit like "don't listen to ppl with no experience in microservices, i dont have experience with microservices, go buy my book about microservices".

Matthias Noback (Speaker) at 20:17 on 1 Jul 2017

@hgraca I'm very sorry to have disappointed you. My talk revolved around the idea that (micro)service architecture shouldn't be dismissed as easily as it usually is. I did an awful lot of research trying to make sure I get all the aspects right, while writing a book about it, because I noticed that people are making big mistakes in their architectural decisions.
I explicitly did not make this a book-selling talk. I didn't even have a slide about it, because I was afraid to get this kind of feedback. But, I would be crazy not to mention it. To be clear: I don't get any money for speaking at DPC. In fact, I work literally hundreds of hours for free to speak at events like DPC. I hope this gives a bit more context.

Deniz Zoeteman at 20:49 on 1 Jul 2017

A good talk to give more insight into microservice architecture, and some pointers to have it not fail. It was quite opinionated though. With the points mentioned that are "required" (though for sure microservice arch enables and promotes these things!), like message bus queue and CD, I disagree they would be required, though certainly useful.
I also think you should maybe change the title for the talk; I was expecting something more in-depth regarding deployment of microservice architecture. And so for me as someone who already knows quite a lot about the points you mentioned, the talk didn't really deliver what I imagined.

Erik de Bos at 22:08 on 1 Jul 2017

A quite thorough breakdown of microservices. Focused on the practical side and drawing from diverse topics such as TDD, CI, etc. Great talk which brings the microservice hype back to the ground.

As always enjoyed listening to Matthias. Good talk with a lot of good pointers to look at on a higher architectural level. Especially the async messaging is something that is often forgotten; leaving people with a distributed monolith.

Martijn at 08:58 on 3 Jul 2017

Maybe not as technical as I would have liked it, but I think that is what Matthias intended to do from the beginning.

Having said that, it did give me pointers to think about to create logical boundaries in the services we would like to create. And above all, not to create services that are to small.

The messages part seemed obvious to me, but I think that part can easily be forgotten by others.

Most of the talk was about very basic principles.

Ben Dechrai at 03:29 on 5 Jul 2017

Matthias's talk gave a good overview of microservices, their benefits, and the ways in which we can adopt them in new projects and existing systems alike. As a proponent of microservices and SOA myself, I enjoyed the talk, and found the information to be clear and easily applicable.