Please log in to watch this conference skillscast.
When should you use microservices? Netflix started to evangelise the approach some time ago and in January, Martin Fowler and myself published an article on the topic covering our thinking and experiences the last few years. It has rapidly become one of the most talked about techniques on the interwebs. Opinions range from “it’s just SOA, move along”, to “they are the awesome”, to “you must be insane”. In order to understand when they might be useful - what problems they solve and why - we need to at least to understand what is meant by microservice architecture, before semantic diffusion claims the term in all it’s ignominy.
In this talk, James Lewis will examine the characteristics of the microservice style using examples from projects over the last few years. Topics covered include the reasons you might want to split an application (or not), the benefits and the drawbacks of the style based on these experiences. Remember though, Rule 16. Distrust all claims for "one true way.”
YOU MAY ALSO LIKE:
- LDNUG September 2017 - #ProgNET Special with Richard Campbell (in London on 12th September 2017)
- Progressive .NET 2017 (in London on 13th - 15th September 2017)
- London Unreal Engine Meetup (in London on 20th September 2017)
- Fast Track to F# with Tomas Petricek & Phil Trelford (in London on 16th - 17th October 2017)
Microservices - choices and challenges
James Lewis is a Principal Consultant for ThoughtWorks UK. He has helped introduce evolutionary architecture practices and agile software development techniques to various blue chip companies: investment banks, publishers and media organisations. James studied Astrophysics in the 90’s but got sick of programming in Fortran.