In The Spotlight
IBM i has been around for many years, and many legacy applications run on the platform. By implementing Kafka, a distributed platform that enables near-real-time communication between systems in different locations, you can use an event-driven architecture alongside your IBM i application when designing a distributed communications system, rather than treating it as a legacy system.
By Joydip Kajilal
IBM i applications have processed business transactions reliably for decades, providing reliable, high-volume batch processing. Many IBM i shops also run interactive transaction processing, real-time database queries, and modern web and API workloads on the same platform. These applications have run high volumes of batch jobs on schedules such as end-of-day settlement processing, daily inventory reconciliation, file transfers, and many other jobs.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online