Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
In this podcast, Gregg discusses architectural considerations for zIIP exploitation. The podcast runs for 2:31.
To listen to the podcast, please click on the following link: http://blogs.datadirect.com/media/GreggWillhoit_BestPracticeszIIPExploitation_1.mp3
What are some of the best practices for zIIP exploitation?
Some of the best practices for zIIP exploitation begin with the actual philosophical approach to exploiting the zIIP. And that is, exploiting the zIIP in a holistic fashion. That is, an architecture which allows for zIIP exploitation regardless of the type of interface, regardless of the type of client.
This type of architecture can really only be achieved in a product architecture delivered by a single company. You can’t achieve this type of zIIP exploitation, for example, if your product depends on distributing or partnering with another product. This kind of zIIP exploitation requires a unified platform, like DataDirect Shadow for example. And what I mean by this is that some of the major benefits to zIIP exploitation are derived from the use of middleware products to access non-relational data and/or relational data on the mainframe.
The various clients that use this data are typically Web services clients, ADO.NET, JDBC and ODBC. And even from the event side, that is publishing out the XML, change data capture all under a single unified platform. So the only way to truly achieve across the board zIIP exploitation for these major categories of product type, or functional categories in middleware or z/OS, is to have a single unified platform all from one vendor. DataDirect Technologies’ Shadow product can then provide you with zIIP exploitation that is end to end, basically almost achieving 100% offload of the code that executes in the vendor’s address space. That is the vendor’s code or IBM’s z/OS code.
In order to fully exploit the zIIP across product offerings, a company needs basically to take this holistic strategy. And this holistic strategy has as its number one requirement that all products that are offered are developed under the same architecture. One cannot rely on the zIIP if one is relying on partnerships to access SQL to non-relational, for example, one cannot rely on that partnership. One cannot rely on the different vendor to have the same goals with regards to zIIP offloads as the company requesting it. That company may have different goals with regards to zIIP offloads. They may have financials that require that they can’t zIIP offload. They may have technical limitations to the architecture since there is no sure architecture that keeps them from offloading to the zIIP. So it’s absolutely incumbent, and a requirement if you will, for a company if they want to achieve across the board zIIP offload, that is for SOA , SQL and events, to do so under a single unified platform.
View all posts from Gregg Willhoit on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.