Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Practical DevOps, Second Edition

You're reading from   Practical DevOps, Second Edition Implement DevOps in your organization by effectively building, deploying, testing, and monitoring code

Arrow left icon
Product type Paperback
Published in May 2018
Publisher Packt
ISBN-13 9781788392570
Length 250 pages
Edition 2nd Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
joakim verona joakim verona
Author Profile Icon joakim verona
joakim verona
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Title Page
Packt Upsell
Contributors
Preface
1. Introducing DevOps and Continuous Delivery 2. A View from Orbit FREE CHAPTER 3. How DevOps Affects Architecture 4. Everything is Code 5. Building the Code 6. Testing the Code 7. Deploying the Code 8. Monitoring the Code 9. Issue Tracking 10. The Internet of Things and DevOps 1. Other Books You May Enjoy Index

Architecture rules of thumb


There are a number of architecture rules that may help us understand how to deal with the previous undesirable situation.

The separation of concerns

The renowned Dutch computer scientist, Edsger Dijkstra, first mentioned his idea of how to organize thought efficiently in his paper from 1974, On the role of scientific thought.

He called this idea the separation of concerns. To this date, it is arguably the single most important rule in software design. There are many other well-known rules, but many of them follow from the idea of the separation of concerns. The fundamental principle is simply that we should consider different aspects of a system separately.

The principle of cohesion

In computer science, cohesionrefers to the degree to which the elements of a software module belong together.

Cohesion can be used as a measure of how strongly related the functions in a module are. It is desirable to have strong cohesion in a module.

We can see that strong cohesion is another...

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
Visually different images