Packt+ | Advance your knowledge in tech

You're reading from Practical Site Reliability Engineering Automate the process of designing, developing, and delivering highly reliable apps and services with SRE

Product type Paperback

Published in Nov 2018

Publisher Packt

ISBN-13 9781788839563

Length 390 pages

Edition 1st Edition

Tools

Docker

Concepts

Configuration Management

Authors (3):

Pethuru Raj Chelliah

Shailender Singh

Shreyash Naithani

View More author details

Table of Contents (14) Chapters

Preface

1. Demystifying the Site Reliability Engineering Paradigm

2. Microservices Architecture and Containers FREE CHAPTER

3. Microservice Resiliency Patterns

4. DevOps as a Service

5. Container Cluster and Orchestration Platforms

6. Architectural and Design Patterns

7. Reliability Implementation Techniques

8. Realizing Reliable Systems - the Best Practices

9. Service Resiliency

10. Containers, Kubernetes, and Istio Monitoring

11. Post-Production Activities for Ensuring and Enhancing IT Reliability

12. Service Meshes and Container Orchestration Platforms

13. Other Books You May Enjoy

Leave a review - let other readers know what you think

Resilient microservices

We touched on microservices briefly in the previous chapter, but we'll just go through a quick summary again here to remind ourselves. Microservices is an architecture style in which large, complex software applications are composed of one or more smaller services. Each of the services are called microservices and deploy independently of one another, without us needing to know the implementation behind the other microservices. Each service works as a single business function that is loosely coupled, small, focused, language-neutral, and has a bounded context.

Resilient microservices can be defined as having the ability to recover back to a working state after a failure or outage. Resilience is one of the main advantages of microservices. Unlike monolith systems, where if something breaks, it will damage the whole application, in microservices, it will only impact that particular functionality, and other services in the application will run as usual.