Last October I had the great chance to attend to JAX London Conference 2016. I will publish a new series of schematic articles with all the notes taken during the sessions. The idea for this series is to simply present a list of links, main ideas and short notes that I believe summarise the content of each session. These notes are just the basic reference from where we could expand our investigations and discussions. Please feel free to add your comments below and I promise you to update the notes with full credits to any contributor.

First of all, I have to reference the JaxCenter as the main publisher for the conference. Specifically, the following link is a good summary of the key insights of the conference.

Notes for the 10th October 2016:

Most of the content of the workshop comes from articles in the Microservices.io, the website with top content about Micro-service architecture patterns and best practices.

The key concept to approach Micro-services architectures with success is to balance out “organization + process + architecture” in order to support distributed solutions philosophy. This idea is expanded in this article.

“Successful software development requires the right organizational structure, development processes, and software architecture.”

Drawbacks:

Using Micro-services architecture is not a free lunch. It is hard and all the drawbacks have to be properly evaluated by the hole team before implementing.

Increase in complexity due to dealing with new issues to solve like inter process communication, partial failure against services not ready, private data per each micro service which requires event driven architecture.

There are powerful tools, PAAS, etc.. .Those require considerable learning curves. It may be required careful coordination across services for some features. And some other risks like high latency issues.

That was all for this session. I hope it helps, please leave a comment if you would like to add something.