In the large part, I’ve stopped running these training courses now – I’ve sort of handed the mantle over to Sam Newman, author of Building Microservices and who co-developed the original training course. I could dust of the old material if you really want, and while the slides are a bit dated, the content is as relevant as ever.
These training courses can be delivered as a 1/2, 1 or 2 day course. The more time we spend, the more depth will be covered of course. For the half day version we will cover a subset of the modules listed in the course description. The course is experiential for the participants but isn’t writing code.
The accepted wisdom for 40 years has been to write programs that do one thing and do it well, yet we have spent the last decade building monolithic applications and communicating via bloated middleware, hoping that Moore’s law keeps helping us out.
There’s a better way: microservices—tiny applications communicating via the Web’s uniform interface with single responsibilities and installed as well-behaved operating system services.
In a workshop aimed at developers, architects, technical leaders, operations engineers, and anybody interested in the design and architecture of services and components, James explores a consistent and reinforcing set of tools and practices rooted in the the Unix philosophy of small and simple for transitioning to microservices.
What you’ll learn:
– The core characteristics of microservices
– Learn about the different types of microservice architecture
– How to apply principle-driven evolutionary architecture techniques
– Capability modeling and the town planning metaphor
– Learn about REST, web integration, and event-driven systems of systems
– Versioning, consumer-driven contracts, and Postel’s law
– Testing, building, and continuous delivery of microservices
– Designing for reliability and applying architectural safety patterns
Micro services – evolutionary approaches for building systems of systems
“Write programs that do one thing and do it well. Write programs to work together” was accepted 40 years ago yet we have spent the last decade building monolithic applications, communicating via bloated middleware and with our fingers crossed that Moore’s Law keeps helping us out. There is a better way.
Micro services. In this tutorial we will discover a consistent and reinforcing set of tools and practices rooted in the the Unix Philosophy of small and simple. Tiny applications, communicating via the web’s uniform interface with single responsibilities and installed as well behaved operating system services. So, are you sick of wading through tens of thousands of lines of code to make a simple one line change? Of all that XML? Come along and check out what the cools kids are up to (and the cooler grey beards).
In this tutorial we will cover the following topics:
- Principle-driven evolutionary architecture
- Capability modelling and the town planning metaphor
- REST, web integration and event-driven systems of systems
- Micro services, versioning, consumer driven contracts and postels law
- Testing, Building and continuous delivery
- Operational concerns
I’ve given up on keeping the history up to date after 2014! This course was run many many times and I’ve not even included NDC in the list.
These were the early, halcyon days of microservice 😉