Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Practical Site Reliability Engineering

You're reading from  Practical Site Reliability Engineering

Product type Book
Published in Nov 2018
Publisher Packt
ISBN-13 9781788839563
Pages 390 pages
Edition 1st Edition
Languages
Authors (3):
Pethuru Raj Chelliah Pethuru Raj Chelliah
Profile icon Pethuru Raj Chelliah
Shreyash Naithani Shreyash Naithani
Profile icon Shreyash Naithani
Shailender Singh Shailender Singh
Profile icon Shailender Singh
View More author details

Table of Contents (19) Chapters

Title Page
Dedication
About Packt
Contributors
Preface
1. Demystifying the Site Reliability Engineering Paradigm 2. Microservices Architecture and Containers 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 1. Other Books You May Enjoy Index

Microservice design principles


There are several different microservices design principles available. Different terms are likely to be used in different places. In this book, we will refer to the microservices design principles as follows:

  • High cohesion among services: A microservice should have one single focus and the sole responsibility for that action. It should not change as a result of other related services. Services should be easily rewritable so that we can achieve scalability, reliability, and flexibility. It should handle a single business function and domain-specific functionality.
  • Autonomous service: A service should independently handle its work without the help of any other services. It should not be tightly integrated with any other service; it should remain loosely coupled in nature. By autonomous, we mean that a microservice should not change because of the external components with which it interacts. Autonomous services honor contracts and interfaces. They should be stateless...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}