We will meet at 6:30pm at AutoScout24 with drinks and pizza.
The talk starts at 7pm and will be in English.
James Lewis: Microservices - choices and challenges
After the talks we have time for drinks and conversations.
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.”
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.
As a member of the ThoughtWorks Technical Advisory Board, the group that creates the Technology Radar, he contributes to industry adoption of open source and other tools, techniques, platforms and languages. For the last few years he has been working as a coding architect on projects built using microservices; exploring new patterns and ways of working as he goes.
James has spoken at a number of UK and international conferences. His favorite topics range from domain driven design, SOA and the future of the web to agile adoption patterns and lean thinking. He’s also heavily involved in the fledgling microservice community. He rather likes the fact that he got to describe his take on things jointly with Martin Fowler in an article that is influencing how people see the future of software architecture.
Location: Events over Munich (http://www.events-over-munich.de/fileadmin/user_upload/pdf/Anfahrt_Events_over_Munich.pdf)