Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Integration Key to Experience: Container Platform Essentials (Part 5)

DZone's Guide to

Integration Key to Experience: Container Platform Essentials (Part 5)

This article has reached the core elements in the blueprint (container platform and microservices), which are crucial to the generic architectural overview.

· Integration Zone ·
Free Resource

Download Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.

In my previous article from this series, we looked into the details that determine how your integration becomes the key to transforming your customer experience.

It started with laying out the process of how I've approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it's time to cover various blueprint details.Image title

This article has reached the core elements in the blueprint (container platform and microservices), which are crucial to the generic architectural overview.

Architectural Details

Image title

As mentioned before, the architectural details covered here are based on real customer integration solutions using open-source technologies. The elements presented here are then the generic common architectural elements that I've identified and collected in a generic architectural blueprint. It's my intent to provide a blueprint that provides guidance and not deep technical details.

This section covers the visual representations as presented, but it's expected that they'll be evolving visually over time. There are many ways to represent each element in this architectural blueprint, but I've chosen icons, text, and colors that I hope are going to make it all easy to absorb. Feel free to post comments at the bottom of this post or contact me directly with your feedback.

Now let's take a look at the details in this architecture and outline the elements uncovered in my research.

Container Platform

Central to all the research conducted was the use of a container platform for some if not all the microservices and applications associated with the omnichannel solution.

Image title

Without a doubt, the flexibility and consistency provided by a container platform enhance delivery of solutions by the researched development teams. The operations teams became efficient with container deployments, management, and monitoring standardized across multicloud infrastructures.

Within the container platform, the first elements are related to the microservices intended to facilitate front end applications interactions with the rest of the integration services. Specific groups of microservices are touched on that service the externally deployed applications:

  • Front-end microservices (providing access to internal integration microservices)
  • Process facade microservices (providing access to automated integration processes)
  • Other integration applications (providing access to aggregated microservices or other internal applications)
  • Single-sign-on or SSO plugins proliferate for security across the microservices and container platform

The deeper access to internal microservices are the next details we'll examine, touching on integration and data microservices.

Core Microservices

This section of the blueprint highlights a few containerized services and the core microservices.

The process facade microservices expose core process integration functionality that is part of the depicted process servers elements. Most deployments host two for availability and leverage the container platform's load balancing features.

Image title

The integration microservices and integration data microservices provide access to most anything in the organization. Imagine mainframes, other third-party helpdesk desktop applications, third-party cloud platform service integration, or whatever your imagination can come up with. Data integration can be container native storage, third-party products, or traditional storage components found in any architecture.

An SSO server element is shown to complete the story of what's backing the connectivity from microservices to the authentication and authorization back-end system(s) that one encounters in an organization.

The final items shown here are special instances of storage labeled real-time data storage, which were part of a solution researched that included integration services requiring special performance storage in containers to stream video to external applications. Interesting enough to include here, though one would expect it in the storage services.

These details are not all-knowing but should give you the guidance you'd need to get started on your own architectural situations.

What's Next

This overview covers the container platform elements that make up our architecture blueprint for omnichannel customer experience use case. 

An overview of the series on omnichannel customer experience portfolio architecture blueprint can be found here:

  1. An introduction
  2. Generic common architectural elements
  3. External application details
  4. API management details
  5. Container platform essentials  (this article)
  6. Storage services
  7. Dissecting several specific application integration architectures

Catch up on any articles you missed by following one of the links above.

Follow along as this series takes you through the omnichannel experience blueprint story. Coming up next, taking a look at the generic common architectural elements.

Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat

Topics:
integration ,agile integration ,blueprint ,containers ,container platform ,red hat ,cloud

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}