The Microservice architectural style has become the hot fashion recently. This talk looks at some of the common characteristics of microservice architectures, what (if any) the difference is between microservices and SOA, how big a microservice should be, the trade-offs between a monolithic and microservice architecture, and some essential things you need to have in place when you first go live using this approach. Software Development in the 21st Century (Part 3 of 3) - Originally delivered at ThoughtWorks XCONF 2014 http://www.thoughtworks.com/talks/software-development-21st-century-xconf-europe-2014 Help us caption & translate this video! http://amara.org/v/J2IG/

Comments

1. Hi there, if i multiple services that they work independently ( will they still be called microservice)?
2. each service have different datastore, surely it will detoriate the app performance, because communication is happening over network, which is again a bottleneck.
3. I feel like I could study under this guy.
4. thanks to Martin with a great explanation about micro services, especially when to use, where to use, how to use & not when to use.
5. Nice explanation!!!
6. I love that he points out that asynchronicity increases complexity. I think this fact is often overlooked in software architecture decisions.
7. Where I can get the slides of this presentation?
8. LOL "i dont do any real work anymore" but the work you have done lives on to inspire others :)))
9. A very precise and concise introduction to microservices. Thanks Martin Fowler.
10. The article he mentioned: http://martinfowler.com/articles/microservices.html