IBM i can integrate with Azure, AWS, and SaaS platforms without custom adapters or protocol gymnastics. This post covers five production-ready patterns: REST API layer, message queue integration, DB2 CDC replication, outbound cloud API calls via SYSTOOLS, and IBM Power Virtual Server with Direct Link connectivity.
IBM i has collected detailed performance data for decades — most shops only look at it when something breaks. This post covers Collection Services, QSYS2 health views, DB2 plan cache analysis, structured logging with Pino, Prometheus metrics from PASE, and a practical starting order for adding real observability to any IBM i environment.
IBM i DevOps is not theoretical — Git, Bob, RPGUnit, and GitHub Actions all run on IBM i 7.3+. This post covers moving source to the IFS, automated builds with Bob, CI pipelines via GitHub Actions and Azure DevOps, RPGUnit testing, and a step-by-step progression from manual releases to a working pipeline.
REST APIs are the bridge between IBM i and modern front ends. This post covers every practical option — IAS REST, Node.js in PASE, PHP, RPG CGI, and API gateways — with enough detail to choose the right approach for your environment.
The “should we leave IBM i?” conversation has been happening for twenty years. The shops that handled it well are running modern hybrid architectures in 2026 — IBM i at the transactional core, cloud services handling front ends, analytics, and integration. Here is what that actually looks like.
Most IBM i shops still manage source the same way they did in the 1990s — members in source physical files, no history, no easy rollback. Git changes that. This post covers RDi, VS Code + Code for IBM i, migrating source to the IFS, and a practical Git workflow for RPG and CL development.
IBM i batch jobs are the ones nobody watches — until one fails. This post covers SBMJOB, WRKJOBSCDE, job queues, completion monitoring, and the production patterns that keep overnight processing reliable.
Every RPG developer eventually writes a program that does something it should not. The calculation is wrong. The loop runs
Most RPG programs are written to handle the happy path. The file exists, the record is found, the calculation succeeds,
IBM i has a reputation for being secure. That reputation is earned — the security model is granular, well-designed, and