Technology stack
A technology stack is a collection of technologies and components used together to build, run, and operate a software system.
React in Depth
A technology stack is the set of programming languages, frameworks, libraries, tools, and infrastructure used to build and operate an application.
- How it is used
- Uses a documented stack to coordinate project decisions, collaboration, and onboarding in React development.
- How deep it goes
- Defines the stack, identifies frontend component roles, and gives selection and onboarding guidance rather than an exhaustive setup procedure.
- Examples
- Uses a React UI library's tool inventory and contrasts e-commerce and portfolio stack scenarios.
- What you can do after
- Practice/perform stack selection for project requirements and use a stack description to orient yourself in an existing codebase.
Microservices Patterns, Second Edition
The combination of programming languages, runtimes, frameworks, libraries, and supporting technologies used to build and run an application or service.
- How it is used
- Uses stack choice and evolution to compare monolithic and microservice architectures.
- How deep it goes
- Defines stack categories and versions, distinguishes private from shared technologies, and explains selection and upgrade trade-offs.
- Examples
- Illustrates different service stacks with Java, Spring Boot, Postgres, MySQL, and Redis, and describes application-wide JVM upgrades.
- What you can do after
- Evaluate stack flexibility and upgrade options against governance needs and distributed-system costs.
Read how Microservices Patterns, Second Edition explains technology stack →
Think Like a CTO
A technology stack is the set of programming languages, frameworks, infrastructure, and other technologies used to build and operate a software system.
- How it is used
- Frames CTO technology choices and acquisition due diligence around long-term support, team capability, cost, and disruption.
- How deep it goes
- Provides assessment questions and legacy-system scenarios, but does not prescribe a stack or explain implementation details.
- Examples
- Uses decades-old Cobol systems and an IBM RPG system accessed through green-screen terminals as legacy examples.
- What you can do after
- Evaluate/understand it by checking team familiarity, supportability, recruitment, and rewrite cost during acquisition due diligence.
Coding with AI
A tech stack is the set of technologies selected to build and operate a software application.
- How it is used
- Uses conversational prompting to explore and refine frontend, backend, and database choices during application planning.
- How deep it goes
- Explains stack selection through prompts and high-level setup steps, but stops short of detailed implementation.
- Examples
- Demonstrates TODO and HAM radio practice-test applications using Flask alongside Vue, MariaDB, PostgreSQL, or MySQL.
- What you can do after
- Apply it via ChatGPT to propose, constrain, and expand an application’s technology choices and initial implementation plan.
Build Your Own Robot: Using Python, CRICKIT, and Raspberry Pi
A hardware and software stack is a layered model of the hardware and software components that together provide a computing system's functionality.
- How it is used
- Organizes robot projects by tracing functionality across user interfaces, software, networks, control boards, motors, and sensors.
- How deep it goes
- Maps concrete signal paths among components and interfaces, while deferring detailed assembly and configuration to dedicated guides.
- Examples
- Uses robot shells, web controls, keyboards, joysticks, cameras, servo motors, DC motors, and QR-code detection as concrete stack configurations.
- What you can do after
- Operate/configure robot interfaces and connections that carry commands from users or cameras to motors and other physical components.
Read how Build Your Own Robot: Using Python, CRICKIT, and Raspberry Pi explains technology stack →
Quantum Programming in Depth
A software stack is a layered collection of software components that collectively supports application execution on a computing platform.
- How it is used
- Connects quantum algorithms and applications to hardware while supporting development, testing, evaluation, execution, and cloud access.
- How deep it goes
- Defines application, system, and programming-tool roles, but stops short of detailing the lower middle-layer conversion process.
- Examples
- Uses quantum chemistry applications, Q#, Qiskit, Python, qubit allocation, and gate application as concrete examples.
- What you can do after
- Build, test, evaluate, and execute quantum applications across potentially different hardware platforms.
Read how Quantum Programming in Depth explains technology stack →
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.
- How it is used
- Uses technology stacks to match each microservice with appropriate implementation choices.
- 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.
Also covered in
- Claude at WorkIn early access (MEAP)
- Vibe EngineeringIn early access (MEAP)
- AI Agents for Offensive SecurityIn early access (MEAP)
- Grokking Web Application Security
- Writing for Developers: Blogs that get read
What to know first
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
- versioningVersioning is the practice of assigning or maintaining identifiable revisions of artifacts over time so their changes, histories, or compatibility can be tracked.
- business logicBusiness logic is the domain-specific rules, computations, and decisions that determine how a software system processes operations and behaves.
Related concepts
- microservice architectureused by · Microservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
- Reactuses · React is an open-source JavaScript library for building user interfaces from declarative, reusable components.
- technology stack upgradeconfigured by · A technology stack upgrade is a change that updates the programming languages, libraries, frameworks, platforms, or tools used by an application component.
- componentuses · A software component is a modular part of a software system that encapsulates related functionality and interacts with other parts through defined boundaries.
Questions about technology stack
What is technology stack?
A technology stack is a collection of technologies and components used together to build, run, and operate a software system.
Which Manning books explain technology stack?
React in Depth, Microservices Patterns, Second Edition, Think Like a CTO, Coding with AI, Build Your Own Robot: Using Python, CRICKIT, and Raspberry Pi, Quantum Programming in Depth and Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform.
What should I know before learning technology stack?
Manning books that teach technology stack usually introduce deployment pipeline, web application, versioning and business logic first.
What kinds of technology stack are there?
Kinds of technology stack include big data technology stack.
What is technology stack also called?
Technology stack is also called tech stack or software stack.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.






