liveBook · Manning

Technology stack

As explained in Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A technology stack is the combination of tools, software, frameworks, and other technologies used to build an application or service.

A technology stack combines the tools and technologies used to build an application or service. In a microservices architecture, each service can select the stack best suited to its task. section 1.9

Using separate stacks across independently deployed services can support:

  • Fine-grained performance tuning, because heavily loaded services can receive dedicated resources or be scaled independently. section 1.9
  • Lower deployment risk, because a service can be updated or rolled back without affecting the entire application. section 1.9
  • Faster development and troubleshooting, because smaller services are quicker to boot, test, replicate, and diagnose. section 1.9

How Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform covers it

How deep it goes
Explains the operational benefits of choosing stacks per service, but does not identify particular technologies or selection procedures.
Examples
Uses independently scalable microservices, shared or dedicated infrastructure, service updates, and service-level rollbacks as examples.
What you can do after
Evaluate stack choices by considering service workload, scalability, deployment isolation, testing, and troubleshooting needs.
How it connects
Connects technology stacks with microservices, scalability, deployment risk, testing, troubleshooting, and distributed applications.

Also explained in

Compare how 6 books explain technology stack →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform. The section links point to the parts of the book it draws on.