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

Integration Key to Experience: An Introduction (Part 1)

DZone's Guide to

Integration Key to Experience: An Introduction (Part 1)

Follow along as this series takes you through the omnichannel experience blueprint story.

· 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.

For the past few months, I've been digging into integration as the key to the omnichannel experience.

It's an interesting challenge in that I've been given the mission of creating architectural content based on common solution adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the chuff.

What does that mean?

It means that it's going to provide you with a way to implement a solution using open-source technologies by focusing on the integrations, structures, and interactions that actually have been proven to work in the trenches.

What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, and they might not fully deliver on their promises.

Enter the term Architectural Blueprint. Let's look at these blueprints, how their created and what value they provide for your solution designs.

The Process

The first step is to decide the use case to start with, which for me had to be linked to a higher level theme that becomes the leading focus. This higher level theme is not quite boiling the ocean, but it's so broad that it's going to require some division into smaller parts.

This higher level theme is focusing on 'Migrating Applications to Containers,' which gives me the latitude to break it down as follows and in no particular order:

    omnichannel customer experience
  • Omnichannel experience
  • Agile integration for cloud-native applications
  • Leverage API first development and management
  • Integrate SaaS applications
  • Modernize existing applications with microservices

The first case I'm tackling is omnichannel experience.

The approach taken is to research existing solution implementations in this space, collect their public-facing content, research the internal implementation documentation collections from their successful engagements, and where necessary reach out to the field resources involved.

What's Next?

The resulting content targets the following three items.

  • A slide deck of the architectural blueprint for use telling the portfolio solution story.
  • A generic architectural diagram providing the general details for the portfolio solution.
  • A write-up of the portfolio solution in a solution brief format.

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

  1. An introduction (this article)
  2. Generic common architectural elements
  3. External application details
  4. API management details
  5. Container platform essentials
  6. Storage services
  7. Example process integration 
  8. Example mobile integration
  9. More example integration blueprints

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 architecture ,integration ,containers ,container platform ,architecture ,developers ,architects ,omnichannel integration

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}