Testing Microservices When the Stakes Are High
17 Oct 2015
-
Locked
Imagine a financial system that's responsible for transacting thousands of dollars per second, where a 30-second downtime means significant transaction loss not only to us but to our merchants. The key players are performance, reliability and security. Now imagine that network distributed across multiple independent artifacts, where each artifact consists of its own Virtual Machine, database schema and application.
Next imagine rolling this out on a fortnightly basis.
How would you test this? What are the challenges you might face?
The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. In this masterclass, we’ll look at what microservices are, the traditional ways that people talk of testing microservices and how we do it differently.
There are countless ways to show up and contribute. Which one will you try today?
Explore MoT
What I learned about influence by becoming a stakeholder
Gain the tools you need to become an operability advocate. Making your testing even more awesome along the way!
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Comments