Ten servers, ten different ways
A technician sets up ten web servers by hand. By the end, each one is a little different. One has a setting missed. One has an old package.
When the tenth fails, nobody can say what it should look like.
DevOps teams solve this by writing the setup down as code.
Key words
| Word | What it means |
|---|---|
| Microservice | a small separate service that does one job and talks to others |
| Monolith | one big program that does every job in a single piece |
| Infrastructure as code | describing servers and their links in files, so a tool can build them the same way each time |
| Network | computers and devices joined so they can share data |
| Collaboration | working together towards a shared goal |
| Scale | to grow or shrink the power of a system to fit the demand |
| Adapt | to change to suit new conditions |
| Server | a computer that provides a service to other computers |
| Script | a short program that does a job step by step |
The cells students fill in are left blank in this preview.
By the end of this lesson
Note
I can explain microservices, infrastructure as code, communication and collaboration, and adapt and scale.
Starter
Have a go
Starter
3 questionsYour answers are marked here and are not kept. A college account keeps every student’s marks.
Microservices
A monolith is one big program. If one part fails, the whole thing may stop. A change to one part means releasing the whole program.
A microservice design splits the system into small services. Each does one job, such as sign-in, payments or search. Each can be changed, tested and released on its own.
Infrastructure as code
Infrastructure as code means you describe servers and networks in files. A tool reads the files and builds them. Run it ten times and you get ten identical servers.
The files can be saved, reviewed, tested and undone, just like program code.
Check
Have a go
Check
3 questionsYour answers are marked here and are not kept. A college account keeps every student’s marks.