Portability
Portability is the ability to transfer or use software, data, or other artifacts across systems or environments with limited adaptation while retaining their usefulness.
Road to Kubernetes
Portability is the property of software being transferable and usable across different computing environments with minimal modification.
- How it is used
- Supports adaptable software delivery by moving applications across development, CI/CD, production, and hosting environments with less configuration.
- How deep it goes
- Traces portability from CI/CD automation through container images to Kubernetes manifests, while identifying platform and managed-service caveats.
- Examples
- Uses Git-based CI/CD workflows, Docker container images, registries, on-premise or cloud deployments, and Kubernetes manifests as concrete examples.
- What you can do after
- Apply it via CI/CD pipelines, container runtimes, or Kubernetes manifests to package and move applications across environments.
Developer Experience on Kubernetes
Portability is the ability of software or an environment to operate across different machines, platforms, operating systems, or architectures.
- How it is used
- Supports sharing and running development environments across machines, platforms, runtimes, cloud platforms, and IDEs.
- How deep it goes
- Distinguishes specification-level portability from author-controlled portability, using AMD64 versus ARM64 to expose dependency limits.
- Examples
- Uses Homebrew, Windows AMD64, MacBook Pro ARM64, GitHub Codespaces, and a Dev Containers configuration.
- What you can do after
- Operate/configure portable development environments and identify dependencies that restrict supported architectures or platforms.
Read how Developer Experience on Kubernetes explains portability →
Data for All
The characteristic of data that allows it to be transferred or moved between locations, systems, or entities.
- How it is used
- Frames portability as a way to give people more control over moving data between companies.
- How deep it goes
- Explains portability through regulatory provisions and a familiar analogy, without technical implementation details.
- Examples
- Uses mobile phone numbers and continuous data transfers from digital gatekeepers to illustrate portability.
- What you can do after
- Evaluate and understand choices about moving personal data to another company.
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
The ability to move software, data, or workloads between computing environments with limited changes.
- How it is used
- Uses portability as a consideration in the cloudbursting business case.
- How deep it goes
- Discusses provider dependence and the cost of a multi-provider approach, without detailing migration procedures.
- Examples
- Uses Reign.net’s potential use of multiple cloud providers to illustrate reduced dependence and added complexity.
- What you can do after
- Evaluate provider dependence against the added cost and complexity of using multiple clouds.
Modern C, Third Edition
Portability is the ability of software to operate across different platforms or computer architectures with little or no change.
- How it is used
- Uses C’s abstraction and compilation model to write programs that can run across computer architectures.
- How deep it goes
- Explains source abstraction, platform-dependent binaries, standards conformance, and compiler diagnostics, but not portability internals.
- Examples
- Uses compiler commands, a flawed C listing, contrasting gcc and clang diagnostics, and stepwise correction exercises.
- What you can do after
- Apply it via a C compiler by writing correct code, comparing diagnostics, and testing compilation across platforms.
Modern C
Portability is the property of software being usable across different computing environments with little or no modification.
- How it is used
- Uses portability to connect correct C programming with execution across different computer architectures.
- How deep it goes
- Defines portability through platform-dependent binaries and compiler translation, but defers detailed portability rules.
- Examples
- Uses PC, phone, set-top box, and refrigerator examples plus c99, clang, gcc, and icc compilation commands.
- What you can do after
- Evaluate portability by writing correct C, compiling with warnings, and avoiding assumptions validated only on one platform.
Embedded Software with Rust
Portability is the ability of software or development methods to operate across different hardware architectures or platforms with limited adaptation.
- How it is used
- Decouples reusable firmware logic from platform-specific hardware abstraction layer implementations.
- How deep it goes
- Works through trait implementations, reusable LED and UART functions, platform-specific setup, and mock-based testing.
- Examples
- Uses LED blinking on Cortex-M and RISC-V, mock peripherals, and UART echo examples for STM32 and ESP32-C3.
- What you can do after
- Apply embedded-hal traits to write reusable LED-blinking logic across Cortex-M and RISC-V platforms.
Learn Docker in a Month of Lunches, Second Edition
Portability is the ability of software to run consistently across different deployment environments.
- How it is used
- Keeps applications and CI/CD pipelines consistent across environments, reducing drift and easing movement between deployment services.
- How deep it goes
- Explains container packaging, environment-specific behavior, and portable pipeline structure, but stops short of detailed platform implementation.
- Examples
- Uses dependency-packaged containers, Compose smoke tests, Dockerfile unit tests, coordinating scripts, and multi-platform GitHub Actions agents.
- What you can do after
- Apply it via Docker and Compose to reproduce builds, tests, and smoke tests across developer and CI/CD environments.
Read how Learn Docker in a Month of Lunches, Second Edition explains portability →
BDD in Action, Second Edition
Test portability is the property of test automation code that allows it to operate across different contexts or integration tools with limited change.
- How it is used
- Supports reusable test automation across multiple suites, teams, contexts, and integration tools.
- How deep it goes
- Explains layered abstraction and consistent APIs, reaching tool lock-in mitigation without detailing implementation code.
- Examples
- Uses Playwright for component tests and WebdriverIO for cross-browser tests without changing test code.
- What you can do after
- Build reusable tests that switch integration tools without rewriting the existing test suite.
Read how BDD in Action, Second Edition explains portability →
Also covered in
- Server-Side WebAssembly
- Shipping Go: Develop, deliver, discuss, design, and go again
- Designing Deep Learning Systems: A guide for software engineers
- Decision EngineeringIn early access (MEAP)
- Timeless Algorithms, The Foundational IdeasIn early access (MEAP)
- Java Persistence with Spring Data and Hibernate epub
- Digital Twins in Action
What to know first
- applicationAn application is a software program or system that provides functionality or performs tasks for users or other software.
- cloud providerA cloud provider is an organization or service operator that supplies remotely accessible computing resources or services over a network, often on demand.
- hardwareHardware is the physical equipment and components of a computing system, including processors, memory, storage, and peripherals.
- monitoringMonitoring is the ongoing observation and measurement of a system or process to assess its behavior or condition and detect changes, failures, or other problems.
Related concepts
- containeraddressed by · A software container is an isolated execution environment that packages an application and its dependencies, typically sharing the host operating-system kernel.
- Querydsladdressed by · Querydsl is a Java framework for constructing type-safe database queries through a fluent API and generated query types.
- serverless computingcontrasts with · Serverless computing is a cloud execution model in which a provider manages the underlying infrastructure and allocates resources for workloads, typically on demand.
Questions about portability
What is portability?
Portability is the ability to transfer or use software, data, or other artifacts across systems or environments with limited adaptation while retaining their usefulness.
Which Manning books explain portability?
Road to Kubernetes, Developer Experience on Kubernetes, Data for All, The Cloud at Your Service: The when, how, and why of enterprise cloud computing, Modern C, Third Edition, Modern C, Embedded Software with Rust, Learn Docker in a Month of Lunches, Second Edition and 1 more.
What should I know before learning portability?
Manning books that teach portability usually introduce application, cloud provider, hardware and monitoring first.
What is the difference between portability and serverless computing?
Portability is the ability to transfer or use software, data, or other artifacts across systems or environments with limited adaptation while retaining their usefulness. Serverless computing is a cloud execution model in which a provider manages the underlying infrastructure and allocates resources for workloads, typically on demand.
What kinds of portability are there?
Kinds of portability include cloud portability, table-format portability and database portability.
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.








