Portfolio Architecture Examples - Application Development Collection

 

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Portfolio Architecture Examples - Data Engineering Collection

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Portfolio Architecture Examples - Retail Collection

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Portfolio Architecture Examples - Finance Collection

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Portfolio Architecture Examples - Telco Collection

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Portfolio Architecture Examples - Healthcare Collection

Figure 1: The portfolio architecture process

For a few years now we've been working on a project we have named Portfolio Architectures. These are based on selecting a specific use case we are seeing used in the real world by customers and then finding implementations of that case using three or more products from the Red Hat portfolio.

This basic premise is used as the foundation, but many aspects of open source are included in both the process and the final product we have defined. There is a community, where we share the initial project kickoff with a group of architects and use their initial feedback from the start. We also present the architecture product we've created right at the end before we publish to ensure usability by architects in the field. The final publish product includes some internal only content around the customer projects researched, but most of the content is open and freely available through various open source channels. 

This article is sharing an overview of the product we've developed, what's available to you today in our architecture center, and concludes by sharing a collection of architectures we've published.

Intelligent data as a service (iDaaS) - Example data insights

Part 4 - Example HL7 & FHIR integration

In our previous article from this series we talked about the example iDaaS data architecture specifically integration for HL7 and FHIR healthcare standards.

The process was laid out how we approached the use case and how portfolio solutions are the base for researching a generic architecture. It continued by laying out the process of how we approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our exploration of an HL7 and FHIR integration architecture, we'll walk you through a more specific example. This scenario is showing a proven and scalable architecture for integrating data insights into your healthcare solutions.

Intelligent data as a service (iDaaS) - Example HL7 and FHIR integration

Part 4 - Example HL7 & FHIR integration

In our previous article from this series we talked about the example iDaaS data architecture which outlines at a higher abstraction level the solution for any healthcare organisation.

The process was laid out how we approached the use case and how portfolio solutions are the base for researching a generic architecture. It continued by laying out the process of how we approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the example data integration architecture, we'll walk you through a more specific example. This scenario is showing a proven and scalable architecture for integrating HL7 and FHIR solutions into your healthcare organisation.

Intelligent data as a service (iDaaS) - Example data architecture

Part 3 - Example data architecture

In our previous article from this series we talked about the logical common architectural elements found in an intelligent data as a service (iDaaS) solution for the healthcare industry.

The process was laid out how we approached the use case and how portfolio solutions are the base for researching a generic architecture. It continued by laying out the process of how we approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the common architectural elements, it's now time to look at a specific example. This article walks you through an example data integration scenario showing how expanding the previously discussed elements provides an example for healthcare data integration scenarios.

Intelligent data as a service (iDaaS) - Common architectural elements

Part 2 - Common architectural elements

In the previous article from this series we introduced an architecture around intelligent data as a service (iDaaS) for the healthcare industry.

The process was laid out how we approached the use case and how portfolio solutions are the base for researching a generic architecture. 

The only thing left to cover was the order in which you'll be led through the details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

Intelligent data as a service (iDaaS) - Architectural introduction

Part 1 - Architectural introduction

The last few months we have been digging deeply into the world of healthcare architectures with a focus on presenting access to ways of mapping successful implementations for specific use cases.

It's an interesting challenge in that we have the mission of creating architectural content based on common customer 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's 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. 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, might not fully deliver on their promises.

Enter the term Portfolio Architecture. 

Let's look at these architectures, how they're created and what value they provide for your solution designs.

Red Hat Summit Connect and Partner Experience Dublin - Talking Architecture Shop (slides)

The Red Hat Summit Connect Partner Experience and Red Hat Summit Connect events for customers were held this week in Dublin. Each was a one day event,  part of a new series of small-scale events, that brings the discussion of open source technology to your local cities.

The days were intended to bring updates and insights into the latest technologies and also offered the opportunity to get hands on with a few Red Hat technologies.  There were different streams of session topics hosting tech talks led by Red Hat experts and also business focused sessions delivered from local industry leaders including some fantastic partner and customer stories.

I was invited to give a session at both events in Dublin this week and wanted to share the slides presented that included links to all of the available content we discussed. 

Red Hat Summit Connect Partner Experience Dublin - Exploring Open Source Success at Scale

The Red Hat Summit Connect Partner Experience Dublin is a one day event,  part of a new series of small-scale events, that brings the discussion of open source technology to your local cities.

 The day provides updates and insights into the latest technologies and will also offer the opportunity to get hands on with Red Hat technologies.  There will be different streams of session topics that will host tech talks led by Red Hat experts and also business focused sessions delivered from industry leaders including some fantastic partner and customer stories.

I've been invited to give a session in Dublin and wanted to share the planning with you for this event in November. 

Red Hat Summit Connect Dublin - Talking Architecture Shop

The Red Hat Summit Connect Dublin is a one day event,  part of a new series of small-scale events, that brings the discussion of open source technology to your local cities.

 The day provides updates and insights into the latest technologies and will also offer the opportunity to get hands on with Red Hat technologies.  There will be different streams of session topics that will host tech talks led by Red Hat experts and also business focused sessions delivered from industry leaders including some fantastic partner and customer stories.

I've been invited to give a session in Dublin and wanted to share the planning with you for this event in November. 

Retail data framework - Example data architecture

Part 3 - Example data architecture

In our previous article from this series shared a look at the logical common architectural elements found in a retail data framework solution for retail organisations.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

It continued by laying out the process of how we've approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the logical view of the architecture, it's now time to look at a specific example.

This article walks you through an example stock control scenario showing how expanding the previously discussed elements provides an example for your own stock control scenarios.

Retail data framework - Common architectural elements

Part 2 - Common architectural elements

 In our previous article from this series we introduced a use case around the data framework for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

The only thing left to cover was the order in which you'll be led through the details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

This will start our journey into the logical elements that make up the real-time stock control architecture.

Retail data framework - An architectural introduction

Part 1 - An architectural introduction

This article launches a new series exploring a retail architecture. It's focusing on presenting access to ways of mapping successful implementations for specific use cases.

It's an interesting challenge creating architectural content based on common customer 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's 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. 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, might not fully deliver on their promises.

Enter the term Portfolio Architecture. 

Let's look at these architectures, how they're created and what value they provide for your solution designs.

Real-time stock control - An architectural introduction

Part 1 - Architectural introduction

This article launches a new series exploring a retail architecture. It's focusing on presenting access to ways of mapping successful implementations for specific use cases.

It's an interesting challenge creating architectural content based on common customer 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's 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. 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, might not fully deliver on their promises.

Enter the term Portfolio Architecture. 

Let's look at these architectures, how they're created and what value they provide for your solution designs.

Store health and safety - Example health and safety architecture

Part 3 - Example store health
and safety architecture

In our previous article from this series shared a look at the logical common architectural elements found in a store health and safety solution for retail organisations.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. It continued by laying out the process of how we've approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the logical view of the architecture, it's now time to look at a specific example.

This article walks you through an example store health and safety scenario showing how expanding the previously discussed elements provides an example for your own store health and safety scenarios.

Store health and safety - Common architectural elements

Part 2 - Common architectural elements

In our previous article from this series we introduced a use case around headless e-commerce for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

The only thing left to cover was the order in which you'll be led through the details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

This will start our journey into the logical elements that make up the store health and safety architecture.