Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

of

IBM Z for the Digital Enterprise - Microservices, APIs Slide 1 IBM Z for the Digital Enterprise - Microservices, APIs Slide 2 IBM Z for the Digital Enterprise - Microservices, APIs Slide 3 IBM Z for the Digital Enterprise - Microservices, APIs Slide 4 IBM Z for the Digital Enterprise - Microservices, APIs Slide 5 IBM Z for the Digital Enterprise - Microservices, APIs Slide 6 IBM Z for the Digital Enterprise - Microservices, APIs Slide 7 IBM Z for the Digital Enterprise - Microservices, APIs Slide 8 IBM Z for the Digital Enterprise - Microservices, APIs Slide 9 IBM Z for the Digital Enterprise - Microservices, APIs Slide 10 IBM Z for the Digital Enterprise - Microservices, APIs Slide 11 IBM Z for the Digital Enterprise - Microservices, APIs Slide 12 IBM Z for the Digital Enterprise - Microservices, APIs Slide 13 IBM Z for the Digital Enterprise - Microservices, APIs Slide 14 IBM Z for the Digital Enterprise - Microservices, APIs Slide 15 IBM Z for the Digital Enterprise - Microservices, APIs Slide 16 IBM Z for the Digital Enterprise - Microservices, APIs Slide 17 IBM Z for the Digital Enterprise - Microservices, APIs Slide 18 IBM Z for the Digital Enterprise - Microservices, APIs Slide 19 IBM Z for the Digital Enterprise - Microservices, APIs Slide 20 IBM Z for the Digital Enterprise - Microservices, APIs Slide 21 IBM Z for the Digital Enterprise - Microservices, APIs Slide 22 IBM Z for the Digital Enterprise - Microservices, APIs Slide 23 IBM Z for the Digital Enterprise - Microservices, APIs Slide 24 IBM Z for the Digital Enterprise - Microservices, APIs Slide 25 IBM Z for the Digital Enterprise - Microservices, APIs Slide 26 IBM Z for the Digital Enterprise - Microservices, APIs Slide 27 IBM Z for the Digital Enterprise - Microservices, APIs Slide 28 IBM Z for the Digital Enterprise - Microservices, APIs Slide 29 IBM Z for the Digital Enterprise - Microservices, APIs Slide 30 IBM Z for the Digital Enterprise - Microservices, APIs Slide 31 IBM Z for the Digital Enterprise - Microservices, APIs Slide 32 IBM Z for the Digital Enterprise - Microservices, APIs Slide 33 IBM Z for the Digital Enterprise - Microservices, APIs Slide 34 IBM Z for the Digital Enterprise - Microservices, APIs Slide 35 IBM Z for the Digital Enterprise - Microservices, APIs Slide 36
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

0 Likes

Share

Download to read offline

IBM Z for the Digital Enterprise - Microservices, APIs

Download to read offline

IBM Z for the Digital Enterprise - Microservices, APIs

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

IBM Z for the Digital Enterprise - Microservices, APIs

  1. 1. APIs and Microservices on Z
  2. 2. So, you want to respond to business requirements more quickly? 2 The services you provide are not seen as transforming to meet new business needs fast enough. Your existing application structure means it takes too long and carries too much risk to change fast. Your development process imposes unacceptable delays. Your teams are not accepting of agile practises and are not aligned or empowered to keep ahead of business needs You've heard from companies which "need greater agility and scalability" are using Microservices to achieve "fast time to market and improved app quality" by using them to "prioritize the continuous delivery of single-purpose services".
  3. 3. 3 Microservices is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities. The microservice architecture enables the continuous delivery/deployment of large, complex applications. It also enables an organization to evolve its technology stack. From Chris Richardson (Microservice.io) What are microservice?
  4. 4. Why create microservices? 4 For fast time to market and improved app quality (IBM Cloud Garage Method). To prioritize the continuous delivery of single- purpose services. Becoming popular with companies that need greater agility and scalability (Pivotal). "balancing speed and safety at scale.”
  5. 5. Key Scenarios on IBM Z 5 Expose services to be consumed by external (micro)services Create new (micro)service to augment existing business logic Extend existing business logic by calling a (micro)service Incrementally refactor monolithic applications towards a microservices architecture Create new applications and services
  6. 6. Expose services to be consumed by external (Micro)services w Microservice comp Silo logic Silo data Microservice comp Microservice component Microservices Application Monolithic Application APIAPIAPIAPI 6
  7. 7. Create new (micro)service to augment existing business logic w Microservice comp Silo logic Silo data Microservice comp Microservice component Microservices Application Monolithic Application APIAPIAPIAPI 7
  8. 8. Augment existing business logic by calling a (micro)service w Microservice comp Silo logic Silo data Microservice comp Microservice component Microservices Application Monolithic Application 8
  9. 9. Incrementally refactor monolithic applications towards a microservices architecture w Silo logic Silo data Application Monolithic Application APIAPIAPIAPI 9
  10. 10. Create new applications and services w Silo logic Silo data Monolithic Application APIAPIAPIAPI 10
  11. 11. You need more knowledge about microservices: Thoughtworks 11https://www.thoughtworks.com/insights/microservices “Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations” - Conway, 1967
  12. 12. 12 An API means the service can be consumed and managed more easily. Microservices = APIs Microservices demand APIs.
  13. 13. 13 A fast and reliable DevOps cycle means the service can continue to meet the business needs whilst maintaining high quality of delivered production instances. Microservices demand APIs.Microservices demand a combination of APIs and DevOps. Microservices = APIsMicroservices = APIs + DevOps
  14. 14. Microservices = APIs + DevOps 14 Microservices = (APIs + DevOps) x Innovation Business need for innovative use of the services drives the demand. Microservices demand a combination of APIs and DevOps where Innovation is rewarded.
  15. 15. Microservices = (APIs + DevOps) x Innovation x Agile Culture 15 Our chief weapon is surprise...surprise and fear...fear and surprise.... Our two weapons are fear and surprise...and ruthless efficiency.... Our *three* weapons are fear, surprise, and ruthless efficiency...and an almost fanatical devotion to the Pope.... Our *four*...no... *Amongst* our weapons.... Amongst our weaponry...are such elements as fear, surprise.... Without an agile culture the services will quickly go stale. Microservices demand a combination of APIs and DevOps where Innovation is rewarded within an Agile Culture.
  16. 16. Microservices in context 16 • An API means the service can be consumed and managed more easily. • A fast and reliable DevOps cycle means the service can continue to meet the business needs whilst maintaining high quality of delivered production instances. • Business need for innovative uses of the services drives the demand. • Do not spend time, effort and money on creating microservices without a proven need. • This makes it crucial that providers engage strongly with their current and potential consumers. • Innovation works both ways - new ways to create, manage and monetise application assets. • Without an agile culture the services will quickly go stale. • A non-agile provider won't keep up with business needs. • A non-agile consumer is less of a problem, but may be required to upgrade to remain in support. • A poor appetite for innovation and agility will be a tougher sales proposition for Microservices.
  17. 17. 17 An API means the service can be consumed and managed more easily. Microservices = APIs Microservices demand APIs.
  18. 18. Expose z/OS assets as RESTful APIs without writing any code
  19. 19. Expose z/OS assets as RESTful APIs without writing any code
  20. 20. z/OS Connect EE Policy-based API processing 21© 2018 IBM Corporation ibm.biz/zosconnect-policy-intro Policy-based API processing gives you an effective way to manage client requests that need to drive different behaviours in the backend program depending on variations in the header of an API request. This gives you the ability, for example, to handle application affinities, where API requests need routing to different regions.
  21. 21. z/OS Connect EE Use API requester to call external APIs from z/OS assets 22© 2018 IBM Corporation
  22. 22. API Enablement Market Dynamics In 1H2018, 50%of B2B interactions were conducted via APIs* 60% of Enterprises see API enablement as critical to their business strategy* On Z this means THOUSANDSof customers will need an API enablement solution in the next few years *Source: https://blog.cloud-elements.com/state-of-api-integration-2018-report-infographic
  23. 23. API Enablement Market Dynamics Since May 50+ Sponsor Users, across 7 industries, have joined the z/OS Connect EE Design Partnership On average 7-10RFEs are raised on z/OS Connect EE month. CICS averages 10-15. z/OS Connect EE is the most popular zTrial by over 300%
  24. 24. z/OS Connect EE IBM z/OS Connect Enterprise Edition 25 Continuous Delivery Updates © 2018 IBM Corporation [3.0.12] August 2018 New APAR fixes [3.0.11] July 2018 Per API Policy • Policies can now be configured for individual APIs [3.0.11] July 2018 Upgraded to Liberty 18.0.0.2 [3.0.10] June 2018 Persistent connections for API Requester from IMS and z/OS Applications • The communication stub for IMS and other non-CICS z/OS applications has been enhanced to automatically enable persistent connections to the z/OS Connect EE server [3.0.10] June 2018 Policy for CICS Services • Use policy to alter cicsCcsid, cicsConnectionRef and cicsTransId dynamically based on HTTP headers in the API request [3.0.9] May 2018 Mapping array type parameters to service fields • You can now add array type HTTP headers, query parameters, and path parameters to your APIs and map them to various service fields. See the change history for details ibm.biz/zosconnect-kc-changehistory
  25. 25. z/OS Connect EE IBM z/OS Connect Enterprise Edition 26 Continuous Delivery Updates Cont. © 2018 IBM Corporation [3.0.8] Apr 2018 DevOps for services, APIs, and API requesters • You can now automate the development, test, and deployment of services, APIs, and API requesters for continous integration and delivery. [3.0.8] Apr 2018 Support for allOf keyword for API Requesters • For users generating artifacts for an API requester, the z/OS Connect EE build toolkit now can process the allOf keyword in a Swagger file. [3.0.8] Apr 2018 API toolkit updated for CICS Context Containers [3.0.8] Apr 2018 Upgraded to Liberty 18.0.0.1 [3.0.7] Mar 2018 CICS Context Containers • CICS service provider services can now be configured to send context containers to CICS programs, providing the program with information about the context in which the service was invoked. [3.0.6] Feb 2018 Upgraded to Liberty 17.0.0.4 [3.0.6] Feb 2018 Dynamic refresh of Policies (update policies without server restart) See the change history for details ibm.biz/zosconnect-kc-changehistory
  26. 26. z/OS Connect EE IBM z/OS Connect Enterprise Edition 27 Continuous Delivery Updates Cont. © 2018 IBM Corporation [3.0.6] Feb 2018 Support for API key security when using API Requester [3.0.5] Jan 2018 Enhancements to API requester to support multidimensional arrays and JSON additional properties in the OpenAPI document [3.0.4] Dec 2017 Enhancements to the RESTful service administration interface • Version 1.1.0 of the interface adds support for POST, PUT, and DELETE methods to support service deployment, service updates, service status updates, and service removal. [3.0.4] Dec 2017 Support for z/OS applications to call an API that is protected by OAuth 2.0 on a request endpoint [3.0.4] Dec 2017 Enhancements to the API toolkit • Version 3.0.3 of the API toolkit supports right-click deployment of service projects, and allows you to view deployed services, examine service properties, update a service, and start/stop a service from the API toolkit. [3.0.4] Dec 2017 Support for imsTranCode override in policy-based API processing • You can now override the IMS transaction code (imsTranCode) that your service invokes at run time. [3.0.3] Nov 2017 Policy-based API processing for APIs that target an IMS application See the change history for details ibm.biz/zosconnect-kc-changehistory
  27. 27. z/OS Connect EE IBM z/OS Connect Enterprise Edition 28 Version 3.0 recap + Continuous Delivery Updates © 2018 IBM Corporation [3.0.3] Nov 2017 CICS® IPIC High availability [3.0.2] Sept 2017 Support for distributed identity propagation to CICS [3.0.2] Sept 2017 New PL/I sample that demonstrates handling large IMS™ data structures [3.0.1] July 2017 Call external APIs from z/OS assets (CICS, IMS, and other z/OS applications) [3.0.0] June 2017 API-enable more IBM z/OS applications • Support for applications with complex data structures, such as REDEFINES and OCCURS DEPENDING ON clauses in COBOL, and REFER option in PL/I. • Support for COBOL and PL/I applications in IMS with large data structures that go beyond traditional message segment limits. New IBM CICS Service Provider • Support for multiple CICS containers, including any mix of BIT- and CHAR-type container. • Exploits IP interconnectivity (IPIC) for cross-LPAR connectivity. z/OS Connect EE API toolkit (Eclipse tooling) • Create and dynamically deploy service artefacts (.sar files) for CICS and IMS. • Rename, redact, and add descriptions to data fields in services.
  28. 28. z/OS Connect EE What’s next for z/OS Connect EE 29 So what are our current priorities? © 2018 IBM Corporation • We prioritise RFEs based on their market appeal (votes from unique clients) and how they align with our strategy • This is a summary of the themes emerging from RFEs in “Uncommitted Candidate” and “Planned for future release” This summarises our current RFE priorities as of October 2018. This deck changes monthly. Please ensure you are viewing the most up to date version. At no point is anything in the RFE process to be taken as a commitment that we will deliver it. Plans and priorities can and will change. Theme Detail Enhanced API Mapping • HTTP Response Code Mapping • Direct to Data (Open API 3.0) Create APIs exactly as your developers want them! Use z/OS Connect EE’s advanced mapping to create the APIs they desire from your Z assets in seconds! • Provide meaningful HTTP response codes on API responses for application error scenarios. Allows customers to create a richer UX around their APIs • Map APIs onto “direct to data” style applications without having to work around issues caused by NULLs, variable structures and field presence. API Monitoring & Request Tracking • Request level monitoring • Request Tracking Keep all your z/OS Connect EE APIs running smoothly using tools like AppDynamics, IBM APM, Splunk and ELK! New integrations with z/OS Connect EE will allow you to monitor your API workloads and quickly identify issues in all your Z SoRs before they become a problem. • Interceptor points to expose detailed information about each API request • Forward tracking ID generation in CICS/IMS can be used for correlation API Requester • JWT support • ID propagation • Expand the set of APIs that can be called from mainframe applications to include those that use JWT as their security mechanism. • Propagate the User ID from the context of the calling application on Z to the API request to achieve a more granular security model. Security • ID assertion for REST and IMS SP • Flow IDs and credentials based on the user calling the API to both IMS and REST endpoints (ID assertion for DB2 is enabled via REST)
  29. 29. Disrupt or be disrupted: innovation at the speed of a startup From above: Technical teams given directive to create more agile, API-based architectures. From the market: FinTech startups presenting increasing threat. 4 Week PoC showed how quickly new services could be delivered 99% zIIP offload ensured cost efficiency REST/JSON made calling z assets the same as any other platform Solved with IBM and z/OS Connect EE 31 Large US Bank 1.5M API requests a day – est. 3M by 2019
  30. 30. Financial Organization In the first 3 months 5500 new savings accounts were opened, with over $150M on deposit. “Opening a savings account went from 2-3 days to 218 milliseconds!” From 2-3 days to 218 milliseconds z/OS Connect EE Real-time account provisioning … deliver this [project] within 2 months!! Accelerated Account Servicing Experiment able to deliver this type of capability to our customers real-time processing! APIs Can Drive New Revenue
  31. 31. We are living through an API revolution 33IBM Z / © 2017 IBM Corporation https://developer.citi.com/
  32. 32. We are living through an API revolution 34IBM Z / © 2017 IBM Corporation https://developer.psa-peugeot-citroen.com/inc/
  33. 33. z/OS Connect EE Demo
  34. 34. z/OS Connect EE

IBM Z for the Digital Enterprise - Microservices, APIs

Views

Total views

272

On Slideshare

0

From embeds

0

Number of embeds

0

Actions

Downloads

17

Shares

0

Comments

0

Likes

0

×