Production
Production is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
Build Python Web Apps with Streamlit
A deployment environment is an isolated live or pre-live instance of an application with its own resources and configuration.
- How it is used
- Deploys locally developed Streamlit apps for users while addressing production dependencies, secrets, and hosting choices.
- How deep it goes
- Explains dependency consistency and walks through Elastic Beanstalk initialization, environment creation, and subsequent deployment.
- Examples
- Uses a requests version mismatch and a Streamlit app deployed through Elastic Beanstalk to illustrate production configuration.
- What you can do after
- Operate/configure a production deployment using requirements.txt and the Elastic Beanstalk CLI.
Read how Build Python Web Apps with Streamlit explains production →
Building Web APIs with ASP.NET Core
A production environment is a runtime deployment context in which an application serves real users or operational workloads.
- How it is used
- Deploys the board-game web API for real requests while separating runtime configuration, credentials, and exposed development tooling.
- How deep it goes
- Explains database preparation, configuration, publishing, endpoint checks, and security verification, but does not detail the entire deployment infrastructure.
- Examples
- Uses appsettings.Production.json, the deployed website, /error/test, /cod/test, and a nonce-based Content-Security-Policy example.
- What you can do after
- Operate/configure a published API with separate database credentials, production settings, direct endpoint tests, and tightened browser security.
Read how Building Web APIs with ASP.NET Core explains production →
LLMs in Production
An operational environment in which a software system or machine-learning model is live and available to perform real work.
- How it is used
- Turns an LLM from a trained artifact into a live service that performs real work for users.
- How deep it goes
- Explains deployment, testing, optimization, and proof-of-concept trade-offs but stops short of detailed infrastructure implementation.
- Examples
- Uses a Raspberry Pi, llama.cpp server, OpenAI-compatible client, quantized model, and customer-facing production tests.
- What you can do after
- Operate/configure a rapid LLM proof of concept, expose it through an API, and identify infrastructure needs before scaling.
Deep Learning with Python, Third Edition
- How it is used
- Serves trained models for prediction by exporting them from training code into a suitable runtime or REST API.
- How deep it goes
- Explains inference-only deployment and model export to TensorFlow Serving or ONNX, with brief guidance on API connectivity.
- Examples
- Uses Keras export and reload examples for TensorFlow Serving and ONNX, plus a mobile app with connectivity constraints.
- What you can do after
- Apply Keras export with TensorFlow Serving or ONNX to serve predictions outside the training Python program.
Read how Deep Learning with Python, Third Edition explains production →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
A production environment is a deployment environment that hosts an application for access by real customers or users.
- How it is used
- Hosts an application for real customers and provides the target for deployments, feedback, and operational workflows.
- How deep it goes
- Explains dependency selection, startup conventions, deployment, environment separation, automation, and blue-green switching; it stops short of detailed infrastructure implementation.
- Examples
- Uses Node.js installation commands, npm start, Kubernetes clusters, Terraform variables, and blue-green DNS switching.
- What you can do after
- Operate/configure production by selecting runtime dependencies, starting a Node.js service, deploying to Kubernetes, and switching environments safely.
Machine Learning Platform Engineering
The live execution environment in which a software system or machine-learning model serves real users or business workloads.
- How it is used
- Frames production as the operational phase that turns validated models into monitored services delivering business value.
- How deep it goes
- Explains automated pipelines, deployment targets, optimization, staging, monitoring, lineage, and rollback without detailing service implementation internals.
- Examples
- Uses REST APIs, edge devices, staging comparisons, optimized deployment artifacts, performance thresholds, and rollback as operational examples.
- What you can do after
- Operate/configure a production ML workflow that deploys, monitors, versions, evaluates, and rolls back models across environments.
Read how Machine Learning Platform Engineering explains production →
Experimentation for Engineers
An operational system serving real users or business processes rather than an offline or test environment.
- How it is used
- Anchors experimental optimization in systems serving real users and business processes.
- How deep it goes
- Distinguishes offline evaluation from online measurement on live systems, stopping short of implementation internals.
- Examples
- Uses search servers, data transformation timing, response latency, and bounce rate as operational examples.
- What you can do after
- Evaluate changes by screening them offline, measuring business metrics in production, and retaining improvements.
Read how Experimentation for Engineers explains production →
Snowflake Data Engineering
A production environment is the environment in which an approved system runs for its intended users and operational workloads.
- How it is used
- Runs approved data pipelines on live data and serves required structures to downstream consumers.
- How deep it goes
- Defines production responsibilities and environment progression, but stops short of detailed deployment commands or configuration procedures.
- Examples
- Uses a bakery pipeline ingesting operational data and JSON orders, with testing based on representative volumes, integrity, and governance needs.
- What you can do after
- Operate pipelines for live workloads while separating development, testing, acceptance, and release activities.
Kargo in Action
A production environment is the operational environment that serves software to its real users or dependent systems.
- How it is used
- Uses production as the final destination in a staged image-promotion workflow reconciled by Argo CD.
- How deep it goes
- Places production in an end-to-end workflow but does not detail its specific configuration or operations.
- Examples
- Follows a container image as it advances through dev and staging into production.
- What you can do after
- Operate a promotion workflow that advances an image through dev, staging, and production.
Also covered in
- Think Like a CTO
- Learn Docker in a Month of Lunches, Second Edition
- Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
- Troubleshooting Java, Second Edition
- Grokking Simplicity
- Grokking Software ArchitectureIn early access (MEAP)
- Delivering Machine Learning Projects: From design to deployment
- Software Engineering for Data ScientistsIn early access (MEAP)
- ASP.NET Core in Action, 3e
- Pro ASP.NET Core 7, Tenth Edition
- Kafka for Architects
- Kubernetes for Developers
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.
- versioningVersioning is the practice of assigning or maintaining identifiable revisions of artifacts over time so their changes, histories, or compatibility can be tracked.
- contractA contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- benchmarkA benchmark is a defined, repeatable task, workload, test, dataset, or reference standard used to measure or compare systems or methods under specified conditions.
Related concepts
- staging environmentcontrasts with · A staging environment is a pre-production computing environment used to validate software or operational changes under conditions that approximate production.
- Kubernetesuses · Kubernetes is an open-source platform for orchestrating containerized workloads and automating their deployment, scaling, and management.
- remote debuggingcontrasts with · Remote debugging is the interactive inspection or control of a program running in a different process or environment from the debugger.
- environmentkind of · An environment is the external context, system, or conditions within which an agent or application operates and interacts.
- execution environmentcontrasts with · An execution environment is the computational context in which a program runs, including its supporting software, available resources, and relevant system state or configuration.
- test environmentcontrasts with · A test environment is a configured computing context, including relevant software, hardware, data, and settings, in which software is executed and evaluated.
Questions about production
What is production?
Production is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
Which Manning books explain production?
Build Python Web Apps with Streamlit, Building Web APIs with ASP.NET Core, LLMs in Production, Deep Learning with Python, Third Edition, Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform, Machine Learning Platform Engineering, Experimentation for Engineers, Snowflake Data Engineering and 1 more.
What should I know before learning production?
Manning books that teach production usually introduce deployment pipeline, versioning, contract and benchmark first.
What is the difference between production and staging environment?
Production is the live operational setting in which a deployed software system serves its intended users or processes real workloads. A staging environment is a pre-production computing environment used to validate software or operational changes under conditions that approximate production.
What is production a kind of?
Production is a kind of environment. An environment is the external context, system, or conditions within which an agent or application operates and interacts.
What is production also called?
Production is also called prod.
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.








