Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Azure for Architects

You're reading from   Azure for Architects Implementing cloud design, DevOps, containers, IoT, and serverless solutions on your public cloud

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781789614503
Length 536 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Ritesh Modi Ritesh Modi
Author Profile Icon Ritesh Modi
Ritesh Modi
Daniel Andres Pelaez Lopez Daniel Andres Pelaez Lopez
Author Profile Icon Daniel Andres Pelaez Lopez
Daniel Andres Pelaez Lopez
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Getting Started FREE CHAPTER 2. Azure Solution Availability and Scalability 3. Security and Monitoring 4. Cross-Subscription Deployments Using ARM Templates 5. ARM Templates - Modular Design and Implementation 6. Designing and Implementing Serverless Solutions 7. Azure Integration Solutions 8. Cost Management 9. Designing Policies, Locks, and Tags 10. Azure Solutions Using Azure Container Services 11. Azure DevOps 12. Azure OLTP Solutions Using Azure SQL Sharding, Pools, and Hybrid 13. Azure Big Data Solutions Using Azure Data Lake Storage and Data Factory 14. Azure Stream Analytics and Event Hubs 15. Designing IoT Solutions 16. Other Books You May Enjoy

Understanding the Single Responsibility Principle

The Single Responsibility Principle is one of the core principles of SOLID. It states that a class or code segment should be responsible for a single functionality and that it should own that functionality completely. The code should change or evolve only if there is a functional change or bug in the current functionality and not otherwise. This code should not change because of changes in some other component or code that is not part of the current component.

Applying the same principle to ARM templates helps to create templates that have the sole responsibility of deploying a single resource or functionality instead of deploying all resources and a complete solution.

Using this principle will help you create multiple templates, each responsible for a single resource or a smaller group of resources rather than all resources.

...
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 $19.99/month. Cancel anytime
Banner background image