Trifork Blog

Axon Framework, DDD, Microservices

GOTO Amsterdam 2015: The Microservices track

April 29th, 2015 by
|

Big hypes, clear trends and micro services

aFewTrends

When we started discussing the tracks for GOTO Amsterdam in november 2014, we took Gartners Hype cycle and used it to plot technologies we had on our radar. It sort of looked like the picture found above. We see Microservices as a very interesting topic. It was Martin Fowler and James Lewis who raised more awareness in this article.

The term “Microservice Architecture” has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. While there is no precise definition of this architectural style, there are certain common characteristics around organization around business capability, automated deployment, intelligence in the endpoints, and decentralized control of languages and data.

Was it the article or was the market ready for Microservices? The trend is very clear in this google trend:

microservicesTrend

The technology trend is clear, when will the market adopt that new technology? We plotted the microservices trend quite early on the hypecycle last year and the main question was; when will it catch on? Jobs are always a good indication if a new technology is being adopted.

microservicesIndeed

The indeed graph is quite clear; Microservices are about to take off.

When looking at Europe, England is one of the first countries to start using a new technology. The rest of Europe catches up in 6-8 months after that. Microservices where a big hit at QCon London (march 2015) and the Microservices  Conference (november 2014).  In short: we believe that starting this summer, microservices will be taking off in Holland. GOTO Amsterdam would be the ideal place to kickstart your microservices knowledge.

 

In James Lewis and our own Sven Johan we found a great combination to shape the microservices track. Sven organizes the Microservices Amsterdam Meetup and is part of our program committee. In the next section, their Microservices track is explained.

Shaping the microservices track

microservicesProgram

The idea of Microservices gives us big promises, but do also bear a lot of risk. In times of continuously delivery Microservices give us the freedom to release functionality independantly and quickly without the risk of retesting the whole application. They allow us to choose the right tool for the job – the right database, the right programming language, the right protocols, build tools, etc. No lame compromises anymore. We are all scared of touching a huge monolith, usually a big ball of mud, because we never know what side-effects our changes will have. Microservices are small and do one thing and that thing really well. They are therefore easy to understand and easy to change. We can even deploy multiple versions of them. We can replace them, if the used technology is not good enough anymore for the problem at hand, without suffering a big rewrite. Services which need to scale can be scaled independently. A microservice is developed by a small team, which chooses the working style they love the most. Another microservice-team may choose another working style.

Should we all move now to Microservices?

Microservices are not a free lunch. You need to be able to rapidly provision infrastructure. After all, it’s not one or two applications you deploy with a shared database, you may deploy 80 different applications and 80 different databases in various versions and some are deployed with multiple instances. You can only do that if you know how to automate the server provisioning. Not only that, your deployment must be automated, too. You need to look at continuous delivery practices like deployment pipelines.

You cannot look at a log file anymore to find out what happened in case of an error. Which log file on which server should it be? Local method calls are no problem compared to remote calls in a cloud environment where machines die all the time. So you need to understand distributed systems monitoring very well in order to hunt down bugs.

All of a sudden, you have distributed transactions. Several data lie on different services in different formats. There’s no nice tool abstracting away the problems you will have in case of failure. You need to explicitely think about it and address it.

microservicesWorkshop

We think that we will see more and more large (legacy) systems moving towards this kind of architecture in the future. This kind of migration is not easy, but GOTO prepares you for this journey. We have a full day track and two full-day workshops on Microservices. Fred George and James Lewis, both early adopters and discoverers of Microservices are hosting their hands-on workshop.

 

Regarding the track

James Lewis, the trackhost, will present on how to develop systems where independent small components live only for a short while until they get replaced by new implementations. Fred George takes us on a journey on how he implemented small collaborating services in various companies and the challenges he faced. Chris Richardson explains how to tackle distributed transactions in an distributed, event-driven architecture. Matt Heath will talk about how they build a large distributed microservice-based system entirely in Go. Wow! Last but now least present Tareq Abedrabbo and Stephen Judd about things they wish they’d known before they started with Microservices – common pitfalls, anti-patterns, but also helpful tools and frameworks.

Want to know more?

Greg Young earlier said about Microservices:

When talking about Microservices we have to remember that they are not new ideas even though they are still at the beginning of the adoption lifecycle, mainly used by innovators and early adopters which brings a lot of enthusiasm. When reaching the early and late majority Greg believes the problems will start to show up with tool vendors and toolkits trying to simplify and sometimes doing things that you really shouldn’t do. The future he sees is that we over the course of 3-5 years will end up rebuilding WS-* the same way Web Services did rebuild all from CORBA. It’s inevitable, we do this over and over again,

source: http://www.infoq.com/news/2014/12/ucon-microservices-future

Do you want to know more? There are 2 great ways to see how deep the rabbithole goes:

1) You can register for our FREE GOTO night with Sam Newman and Uwe Friedrichsen and learn more.

gotoNight

2) You can register now for GOTO Amsterdam 2015 and leverage from the early bird (and use a possible discount code if you look carefully 🙂 )

registernow

 

There is no 3….

Is there another conference in Europe this summer with such a good Microservices track? Nope not yet 😉

We think that GOTO London and GOTO Copenhagen will deliver awesome microservices content though.

JuneCalendar

We hope to welcome you at GOTO and be part of a family of innovators and technology enthusiasts.

1040134_472282589523044_600553998_o

Comments are closed.