February 1, 2017

Service Discovery For Machines And Humans

My slides from the OOP 2017 conference. Abstract: Combining Continuous Deployment and a Microservice architecture brings new challenges to develop and operate your platform. A service discovery enables you to build a flexible system. Developers need to have an up to date view on the deployed services as well. A human readable registry with relevant information is needed. I will outline what we solved with a Service Registry and what impact it had on our architecture. ... Read more

January 15, 2016

How is your microservice architecture doing?

It all started when my new boss stepped into my door and asked me if I had a clue how our system was working. In an ideal world we would have teams and developers who work on a isolated context with clear boundaries. They develop, test, deploy, monitor and operate everything by themselves. They are on 24⁄7 call and therefore they do everything possible that nothing fails. The system is stable and brings in the money. ... Read more

September 29, 2015

Entwicklung verteilter Systeme - Herausforderungen nicht nur an die Architektur

This is my talk about Development of distributed systems - challenges not only for the architecture. You guessed it, it is in german. I gave this talk at BedCon 2015 and I will talk about it again at the Architecture Gathering 2015 in Munich on October 22nd. Abstract: Jede Platform wächst mit der Zeit. Mehr Entwickler mit noch mehr Ideen und Vorstellungen arbeiten alle gemeinsam an der Weiterentwicklung. Das System wird größer und auf viele Systeme verteilt. ... Read more

October 9, 2014

Migrating a monolith

If you start, a monolith is much easier to begin with. Everything is in one place, it’s fast and all team members understand the code. If you plan your application from the start as distributed system in a microservice like style, you add some significant overhead. Don’t do it, monoliths have their advantages at some point. If another team start with the same project or more functionality is added, splitting up the monolith might be a way to go. ... Read more

October 7, 2014

If you don't fight it you end up with a monolith

You planned your software. You talked to your business owners. As soon as you saw a new use case which should be implemented, you modularized it. You did everything right. And then you hit the integration layer. Sounds familiar? At some point in your project you need to integrate all modules with each other. In case of a website you need to produce HTML. There are different approaches how to tackle this problem. ... Read more

October 6, 2014

A Monolith could be good for you

Everybody says monolithic applications are bad. I usually hear things like: Tiny changes need full redeployment (maybe even with downtime) Limited agility Easy to get a big ball of mud So why would you like to have a monolith? There are many definitions of a monolithic application. There are tons for microservices. A Monolith has it’s advantages. There are companies which are successful with monolithic applications. You start faster. ... Read more

October 3, 2014

How you might know that you have a monolith

You start your green field project and keep working on it. It grows and grows and grows. You feel comfortable with it and it could not be better. Because more needs to be done/the product is successful another team is added. If this new team starts complaining that the setup if very complicated and they do take a lot of time to get started: Listen carefully. Of course everybody will complain if they get thrown into another code base, nobody understands the code and of course everybody would have it done differently. ... Read more

© 2009-2017 Oliver Wehrens Impressum