Enterprise Executive 2017: Issue 2 : Page 46

THE BOTTLENECKS TO MAINFRAME DATABASES ARE CAUSED BY ALL THE REQUESTS BEING FUNNELED AND QUEUED THROUGH THE MAINFRAME APPLICATIONS. The Open Access Alternative of the mainframe applications to handle the read-only requests that necessitate manipulation by the application prior to presentation to the front-end applications (see the circled 4 in Figure 1). All other read-only requests can go directly to the database server via API or SOA interfaces (see the circled 5 and 6 in Figure 1). These changes will enable thousands of simultaneous database requests and eliminate the bottlenecks without the need for cloning database copies and experiencing reconciliation and synchronization headaches. The new entrants in the digital economy are driving down transactional costs, which are requiring incumbent organizations to transform their processes and lower their cost structures. Thus, the traditional method of just adding new applications to the existing workloads—which lengthens latency, causes bottlenecks, increases costs and exposes the company to sync and reconciliation risks—is no longer a feasible approach. Business executives will have to redefine their business models to support the new methodologies and low-cost competitors. By employing an open access mainframe database architecture, IT executives and architects will then be able to take the first steps toward becoming a digital enterprise even though most of the data resides in monolithic mainframe databases. IT executives should consider the open access mainframe database model as a way to satisfy current business demands without creating undue risks. Once the mainframe data is no longer bounded by access through existing mainframe applications, IT executives and architects can begin to develop and implement new target architectures that can keep the enterprise competitive over the long term. EE Cal Braunstein is CEO and executive director of research for Robert Frances Group. Additional relevant research and consulting services are available. Email: cbraunstein@rfgonline.com Summary The bottlenecks to mainframe databases are caused by all the requests being funneled and queued through the mainframe applications (see the circled 1 in Figure 1). This needs not be the case. This dependency is a relic of a legacy architecture built decades ago. As stated above the vast majority of transactional requests are read-only, which means these requests could be offloaded from the existing mainframe without modifying the architecture to include database locking. To open the access to the mainframe databases entails creating a back-end mainframe database server (logical or physical) combined with high performance flash (see the circled 2 in Figure 1) and a load balancer (see the circled 3 in Figure 1) that can route all read-only requests to alternate paths. Then one can activate multiple copies 46 | E nt e rp r i s e E xe c u t i ve | 2017: Issue 2

Previous Page  Next Page


Publication List
Using a screen reader? Click Here