Want to eliminate technical debt, deploy every few minutes, use Python, Clojure, and .NET in the same system, and make major rewrites trivially easy? Advocates of microservices designs, such as Martin Fowler, claim that you can do all this and much more if you construct your application as a collection of many tiny components connected via a messaging mechanism. Join Douglas Squirrel for a critical analysis of these claims!
We'll review the brief history of microservices and discuss of the pros and cons of this design style. We will ask questions like: * What are the historical antecedents of microservices architectures and why are they coming to the fore now? * What is the value of unit testing when your units are independent services implemented in 100 lines of code or less? * How might you manage risks in a microservices system, such as unwanted emergent behaviour and component failure? * What might a microservices development team look like? What skills should team members have (or develop) and what roles will they play?
Bring a laptop running a compiler or interpreter for your favourite language if you'd like to try building a working component in a microservices system.
YOU MAY ALSO LIKE:
- Kito Mann's Hacking HTML5 Web Components and Polymer (in London on 10th - 11th July 2017)
- FullStack Bytes with Jolyon Russ! (in London on 25th October 2017)
- F# eXchange 2018 (in London on 5th - 6th April 2018)
Microservices: So Crazy It Just Might Work
Douglas Squirrel has taught 3rd grade, started a one-man business, and performed in comedy sketches. In the last 15 years he has been CTO at startups in financial services and e-commerce and is currently VP Technology at children's payment-card firm Osper.