Scribd
Upload
140 views4 pages

DevOps Landscape

The document outlines the key considerations and components of a DevOps landscape. It discusses factors like coding tools, automation tools, platforms, continuous delivery, and process basics. Process basics includes deploying code through various stages like development, testing, staging, and production and ensuring the ability to rollback. It also emphasizes treating development like a product team focused on ongoing improvement rather than a project team with a short-term mindset.

Uploaded by

Anonymous Hm4IRXEaXd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
140 views4 pages

DevOps Landscape

The document outlines the key considerations and components of a DevOps landscape. It discusses factors like coding tools, automation tools, platforms, continuous delivery, and process basics. Process basics includes deploying code through various stages like development, testing, staging, and production and ensuring the ability to rollback. It also emphasizes treating development like a product team focused on ongoing improvement rather than a project team with a short-term mindset.

Uploaded by

Anonymous Hm4IRXEaXd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Find

things that are unique or critical to DevOps

Considerations Not just programming and systems


management constructs
delivers point in time fix, rarely revisits
project team
"fire and forget"
IDEs
cares about life-span of the product
Focus on thinking like a "product" Languages
team, not a project team
studies how to improve the product product team
Coding Frameworks
"owns" the product
Middleware

product team
Datastores

Developers make build

app tests Project management


Run tests
infrastructure tests Bug tracking
Process Basics ALM tools
Requirement tracking
deploy on "cold" inf.
promote build to staging
run all tests DevOps Landscape Kanban board

re-route production to "cold" inf.

you can rollback to previous one production Automation tools


Configuration & Release management
database upgrades Packaging tools

with microservices, you design things so


microservices
that data upgrades are less of a problem
PaaS
operational metrics to see if app is performing
IaaS
feedback collection
business metrics to see if app is doing
how to improve the product cluster management schemes
the right thing

Plain old Linux

Platforms APM
build
Continious delivery Monitoring log analysis
QA running
Operational middleware node management

things like caches, accelerators, stuff


used in production?

Feedback Analytics
DevOps Landscape
1. Considerations
1.1. Find things that are unique or critical to DevOps

1.2. Not just programming and systems management constructs

2. Coding
2.1. IDEs

2.2. Languages

2.3. Frameworks
2.4. Middleware

2.5. Datastores

3. ALM tools
3.1. Project management

3.2. Bug tracking


3.3. Requirement tracking

3.4. Kanban board

4. Configuration & Release management


4.1. Automation tools

4.2. Packaging tools

5. Platforms
5.1. PaaS

5.2. IaaS
5.3. cluster management schemes

5.4. Plain old Linux

5.5. Operational middleware

5.5.1. Monitoring

5.5.1.1. APM

5.5.1.2. log analysis


5.5.1.3. node management

5.5.2. things like caches, accelerators, stuff used in production?

6. Feedback Analytics
7. Continious delivery
7.1. build

7.2. QA running

8. Process Basics
8.1. Focus on thinking like a "product" team, not a project team

8.1.1. project team

8.1.1.1. delivers point in time fix, rarely revisits

8.1.1.2. "fire and forget"

8.1.2. product team

8.1.2.1. cares about life-span of the product

8.1.2.2. studies how to improve the product

8.1.2.3. "owns" the product

8.1.3. product team

8.2. Developers make build


8.3. Run tests

8.3.1. app tests

8.3.2. infrastructure tests

8.4. promote build to staging

8.4.1. deploy on "cold" inf.

8.4.2. run all tests


8.5. production

8.5.1. re-route production to "cold" inf.

8.5.2. you can rollback to previous one


8.5.3. database upgrades

8.6. microservices

Link: http://www.mindmeister.com/434023134

8.6.1. with microservices, you design things so that data upgrades


are less of a problem
8.7. feedback collection

8.7.1. operational metrics to see if app is performing

8.7.2. business metrics to see if app is doing the right thing

8.7.2.1. how to improve the product

You might also like