Microservices has been a hot topic in recent years as there are many benefits to this architecture, especially in regards to increasing engineering teams velocity and efficiency. While we are already neck deep in microservices, we wish that the 5 videos we’re about to share were around when we started ramping up. After viewing all the youtube videos (or even just some) I’m sure you’ll decide that experimenting with (and then adopting) microservices is worth your while.
James Lewis and Martin Fowler defined Microservices as:
“In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.”
Here are my recommended videos:
1. Martin Fowler – Microservices
Martin Fowler, Chief scientist, Thoughtworks, XCONF 2014
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.
2. Principles Of Microservices
Sam Newman, technologist, Thoughtworks DEVOXX summit 2015. Author of “Building Microsercives” book
Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves: * Modelled Around Business Domain * Culture Of Automation * Hide Implementation Details * Decentralize All The Things! * Deploy Independently * Isolate Failure * Highly Observable In terms of learning outcomes, I’d say that beginners will get a sense of what microservices are and what makes different, whereas more experienced practitioners will get an insight into practical advice into how to implement them.
3. The hardest part of microservices is your data
Christian Posta, Principal Architect, Red Hat at Red Hat Summit 2017. Author of “Microsercives for Java Developers” book
4. Mastering Chaos – A Netflix Guide to Microservices
Josh Evans, Director of Operation Engineering, Netflix, Qcon 2016
Josh Evans talks about the chaotic and vibrant world of microservices at Netflix. He starts with the basics- the anatomy of a microservice, the challenges around distributed systems, and the benefits. Then he builds on that foundation exploring the cultural, architectural, and operational
5. What I Wish I Had Known Before Scaling Uber to 1000 Services • Matt Ranney
Matt Ranney, Chief System Architect, UBER, GOTO summit 2016.
To Keep up with Uber’s growth, we’ve embraced microservices in a big way. This has led to an explosion of new services, crossing over 1,000 production services in early March 2016. Along the way we’ve learned a lot, and if we had to do it all over again, we’d do some things differently. If you are earlier along on your personal microservices journey than we are, then this talk may save you from having to learn some things learn the hard way.