Virtual machine
Includes a full OS, often several gigabytes of overhead for a small application.
It’s the application that adapts to the infrastructure, not the other way round. With NTi Data Provider, deploy containerized .NET applications that are portable and reproducible on any infrastructure.
Your application and everything it needs to run,
isolated from the host system.
Includes a full OS, often several gigabytes of overhead for a small application.
Contains only your code and its dependencies, without a full operating system.
By embedding the runtime and dependencies with the application, the container removes the differences between environments.
What works in development works identically in test and in production.
A platform designed to build,
deploy and run applications across different environments.
.NET runs on Windows, Linux and macOS, as well as on x86, ARM and Power architectures. The same application runs in different environments, unchanged.
Everything the application needs is included in the image: .NET runtime, libraries, configuration. The host simply starts the container.
Microsoft provides maintained and supported base images, to run containerized .NET applications without worrying about the environment.
A .NET application is built once, then deployed identically in development, test and production.
You build an image, then deploy it wherever you want.
A standard .NET application: API, service or console.
The NTi NuGet package opens access to DB2, RPG and CL.
A standard Dockerfile, built on the official Microsoft images.
Run the container on the host of your choice, with nothing to rebuild.
The same image runs on
x64arm64ppc64leAzure · AWS · GCPAny container hostNTi Data Provider is embedded in the .NET application, and therefore in the container.
Nothing to install on IBM i.
Applications run outside IBM i, which is never exposed and keeps its native security mechanisms.
Same image, same runtime, same behavior across all environments.
You duplicate lightweight containers on the .NET side, without putting load on IBM i.
Visual Studio, Git, CI/CD: less dependence on IBM i skills.
Another question? Email us at contact@aumerial.com.
Both approaches are possible. Existing business applications remain on IBM i and can be progressively exposed via containerized .NET services, while preserving RPG and CLP programs or legacy S/36 applications.
New projects can, on the other hand, be developed directly in .NET, with application logic independent of IBM i.
Configuration and sensitive information are handled at the application level, through standard .NET and container mechanisms such as environment variables or configuration files.
No IBM i-side configuration is required.
Yes. Each application runs in its own container, with its own lifecycle and resources.
This approach makes it possible to run multiple workloads around the same IBM i without creating cross-application dependencies.
Yes. IBM i remains isolated, not exposed, and retains all of its native security mechanisms.
The .NET applications run in an environment where security is enforced by the hosting infrastructure, without modifying or bypassing IBM i security rules.
Technically, yes, but with significant constraints.
ODBC and OLE DB providers rely on drivers that are dependent on the operating system and hardware architecture. In a modern, containerized .NET environment, this significantly complicates portability, maintenance, and multi-environment deployments.
NTi relies exclusively on the .NET runtime (CLR) to access IBM i. The application remains 100 % .NET and runs in its own containerized environment, while natively and directly accessing IBM i resources. The same application code is used, with container images built for each target platform (Windows, Linux, ARM, Power, etc.).