Chapter 10. Microservices Architecture: Bit by Bit
How do you make an architecture easier to change? Business is changing faster than ever, and software architectures need to keep up. In this chapter you’ll learn how to create a flexible architecture that can change as your business changes, scale as your business grows, and remain operational even when system failures occur. Intrigued? We hope so, because in this chapter we’re going to show you microservices—an architectural style that solves all of these problems and more. Let’s get started on our journey through microservices, bit by bit.
Are you feeling okay?
StayHealthy, Inc., is a company that specializes in medical monitoring systems for patients in hospitals. Using its systems, doctors and nurses can monitor a patient’s heart rate, oxygen levels, body temperature, blood sugar levels, and more, and even determine whether the patient is sleeping or awake. If something goes wrong, a doctor or nurse is notified right away.
Recent advances in medicine have given rise to a new set of needs for medical monitoring. As a result, StayHealthy plans to leverage newer technology to replace its current patient medical monitoring software with a new system called MonitorMe. Guess what? You’re the architect they chose for the new project.
Below are the requirements for the new system. You’ll need to figure out what kind of architecture ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.
