Self-hosting
Self-hosting is deploying and operating software or services on computing infrastructure controlled or managed by the user or organization.
Kafka for Architects
An on-premises solution is software or infrastructure installed and operated within the customer’s own facilities.
- How it is used
- Frames the production deployment choice for a Kafka cluster against managed cloud and hybrid options.
- How deep it goes
- Compares responsibilities and trade-offs, naming operational tasks without providing a step-by-step installation procedure.
- Examples
- Uses a three-broker Customer 360 cluster and an AsyncAPI topic listing with replication settings.
- What you can do after
- Evaluate/understand when Kafka configuration control justifies in-house infrastructure and operational responsibility.
Think Like a CTO
The provision and operation of software on computing infrastructure owned or controlled at the organization's own premises.
- How it is used
- Frames self-hosting as an infrastructure choice within software purchasing and cloud-versus-on-premises decisions.
- How deep it goes
- Defines the ownership model and examines costs, hosting, capacity, and maintenance without giving hardware installation procedures.
- Examples
- Uses steady intensive computing, seasonal demand, and reallocating private-cloud servers for an online promotion to illustrate workload fit.
- What you can do after
- Evaluate/understand it by weighing workload, existing hardware, capacity limits, purchase costs, and ongoing maintenance.
Grokking AI Applications
Self-hosting is operating an application on infrastructure that an individual or organization owns or directly manages.
- How it is used
- Deploys an application for continuous public or application-to-application access while retaining responsibility for its infrastructure.
- How deep it goes
- Explains ownership, reachability, privacy, cost, and operational complexity, but does not detail hardware specifications or maintenance procedures.
- Examples
- Compares dedicated hardware, a self-managed cloud VM, and managed hosting for a continuously available Langflow application.
- What you can do after
- Operate/configure a self-hosted Langflow deployment and distinguish it from cloud-managed alternatives.
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
On-premises infrastructure is computing and network equipment located within facilities controlled by the organization that operates it.
- How it is used
- Frames infrastructure ownership and facility responsibility before comparing on-premises, colocation, and cloud deployment approaches.
- How deep it goes
- Defines location, ownership, control, and facility obligations, but stops short of configuration or implementation procedures.
- Examples
- Uses company-owned servers and key network devices located within company facilities as the concrete infrastructure example.
- What you can do after
- Evaluate deployment choices by comparing equipment ownership, facility responsibilities, control, and shared-resource access.
Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains self-hosting →
Microsoft Azure in Action
An on-premises system is computing infrastructure operated within an organization's own facilities rather than hosted by a cloud provider.
- How it is used
- Compares self-hosting with cloud infrastructure when choosing how to meet business, security, and data-location needs.
- How deep it goes
- Defines benefits and responsibilities, notes scaling costs, and stops short of covering on-premises operations in detail.
- Examples
- Uses data sovereignty, company-specific security, existing hardware, and a data-center-to-Azure VPN as concrete cases.
- What you can do after
- Evaluate whether data control, security requirements, existing infrastructure, and operational responsibilities support self-hosting.
Related concepts
- cloud computingcontrasts with · Cloud computing is the on-demand delivery of computing resources and services over a network from remotely managed infrastructure.
- hardwareuses · Hardware is the physical equipment and components of a computing system that provide resources for computation and software execution.
- privacyaddresses · Privacy is the protection and controlled handling of information or activities to prevent inappropriate access, collection, use, or disclosure.
- managed APIcontrasts with · A managed API is an interface to a remotely hosted service whose provider operates the underlying software and infrastructure.
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.