GOTO Amsterdam (June 17-19, 2015) is a vendor independent international software development conference with more that 50 top speakers and 500 attendees. The conference covers topics such as AngularJS, Disruption, Docker, Drones, Elasticsearch, Hadoop, Microservices & Scrum.

Tareq Abedrabbo, CTO at Open Credo

Tareq Abedrabbo

Biography: Tareq Abedrabbo

Tareq Abedrabbo is CTO at OpenCredo. His approach is highly pragmatic and hands-on, focusing on finding simple solutions to complex problems.

Tareq has a long-term interest in architecture and service-orientation, most recently microservices. He enjoys building data-driven systems using open source technologies such as Apache Storm, Neo4j, Cassandra and Redis, and is also co-author of Neo4j in action, a comprehensive guide to Neo4j.

Mostly for fun and also in his day-to-day work, Tareq is always learning and applying new programming languages, such as Scala, Clojure, Erlang and Go.

In a previous life, Tareq used to be a committer on Spring Web Services having been involved with the Spring project since its early days. He remains an advocate of the evolving modern Spring stack.

Twitter: @tareq_abedrabbo

Presentation: Things I wish I'd known before I started with Microservices

Track: Microservices / Time: Thursday 15:50 - 16:40 / Location: Effectenbeurszaal

A pragmatic guide

There is no one-size-fits-all approach to building microservices. While a number of common aspirations, goals and techniques have been recognised across different microservices initiatives, the variation in implementation techniques and approaches is substantial. This includes things such as which platform to build the system on, and which tools and frameworks to use. In such a context, essential questions about this architectural style, including whether it is fit for purpose for a particular problem, are more often than not difficult to answer.

Having worked on a number of microservices implementations, large and small, we have recognised recurring patterns and challenges; these we have distilled into a set of pragmatic questions and concerns that developers might face in a similar context. In this presentation we would like to discuss the practical aspects of these questions, illustrated with examples from our own work.

Some of the questions we will be covering include:


  • What's the big deal?
  • Monoliths: friend or foe?


  • Does size matter?
  • Contracts: do we really need to involve legal?


  • Things I wish I'd known before I started
  • Gotchas and anti-patterns