First available 01 April 2019
This video series we follow the experience of the Walmart delivery team as they embrace asynchronous processing patterns in enterprise-grade applications. The series describes the methodology, design and thought process used by Walmart and the considerations of the choices made. By using IBM CICS asynchronous API, Walmart enhanced a complex search capability to achieve large scale transactions in minimal time. This video series is a companion to the IBM Redbooks publication Walmart and the CICS Asynchronous API: An Adoption Experience.
This video series is of interest to:
Walmart has successfully deployed applications that use the IBM CICS asynchronous API and shares their experiences in this video series. In this video we meet the team and are presented with a high level architecture of the solution.
In this video we are introduced to asynchronous processing with the CICS Asynchronous API. We learn the initial problem space Walmart were faced with and how they assessed an ambitious set of requirements to build an Event Processing Service.
At least 1 million records per second was expected to satisfy the minimum requirements of the Event Processing Service. This video describes the initial testing that benchmarked the I/O rates and determined the feasibility of the objective.
It quickly became apparent that serially searching the collection of events would not be sufficient. Response time goals were still out of reach for our initial application. This video explores how Walmart satisfied the SLA by using asynchronous methods to allow searches to run in parallel.
This videos explores the search function that uses the IBM CICS asynchronous API to perform parallel I/O processing. The video also describes the actions that were needed to migrate from the homegrown solution to this new design.
Walmart leverages the CICS asynchronous API in several other ways. This video explores three additional use cases.