Steve Upton

Steve Upton is a software engineer with a background in testing, messaging, and distributed system design. Steve worked at IBM on a variety of projects, from Mainframes to Microservices and was a voting member of the OASIS MQTT Technical Committee. He currently works for HERE Deutschland as a QA Lead on Microservices and IoT systems.
Steve studied Computer Science at Cardiff University and Physics at The Open University.


Learning outcome 

Understand of how, when and why Microservices should be used and importantly, when they shouldn't!
Have a good overview of the technology and practices that make up a successful Microservices system and how they fit together.

What are Microservices and why should you care? Are they a buzzword, a revolution or the new normal? This lecture will look at how Microservices came about and how they fit into the modern software industry. We'll be looking at the good and the bad, trying to offer a honest view on when you should (and shouldn't) use Microservices. We'll examine the technologies and practices that underpin Microservices systems, combining real world examples with practical experience and advice.

Contents of lecture

Part 1
- The 2 histories of Microservices
- What came before?
- What problems are Microservices trying to solve?
- How did the Microservices architecture emerge?

Part 2
- Why you shouldn't do Microservices
- What's hard about Microservices?
- How do we address the challenges of distributed systems?

Part 3
- What Microservices actually look like
- What do Microservices look like in the real world?
 -What technologies underpin them?
- What design patterns are used?
- What practices support Microservices?

- The future of Microservices
- What are the emerging trends in Microservices and why?


  • Active engagement