Cloud factory - Common architectural elements

Part 2 - Common architectural elements

In our previous article from this series we introduced a use case for a cloud factory, deploying multiple private clouds based on one code base using the principles of Infrastructure as Code.

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.

Cloud factory - Architectural introduction

Part 1 - Architectural introduction

This article launches a new series exploring a cloud factory 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.

Remote server management - Example remote architecture

Part 3 - Example architecture

In our previous article from this series shared a look at the logical common architectural elements found in a remote server management solution.

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

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 remote server management scenario showing how expanding the previously discussed elements provides an example for your own remote management scenarios.

Remote server management - Common architectural elements

Part 2 - Common architectural elements

In our previous article from this series we introduced a use case around remote server management 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 cloud adoption architecture.

Remote server management - An architectural introduction

Part 1 - An architectural introduction

This article launches a new series exploring the remote server management 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.

Cloud Adoption - Example adoption architecture

Part 3 - Example adoption architecture

In our previous article from this series shared a look at the logical common architectural elements found in a cloud adoption 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 cloud adoption scenario showing how expanding the previously discussed elements provides an example for your own cloud adoption scenarios.

Getting started with Red Hat Business Automation version 7.11

 This last week the new release of the Red Hat Business Automation products went live, spanning Red Hat Process Automation Manager and Red Hat Decision Manager with a new version 7.11.

These two products provide a lot over versatility to your developer toolbox and there are some getting started documentation and examples to be found in the above linked pages.

Over the years I've shared so many projects and workshops around all the generations of Red Hat Business Automation products, that you might like to have a little overview of the ones that are now fully updated for use?

Below you'll find a walk through the various projects, demos, and workshops available today for you to get started with the latest and greatest of Red Hat Business Automation tools.

Cloud adoption - Common architectural elements

Part 2 - Common architectural elements

In our previous article from this series we introduced a use case around cloud adoption 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 architectural 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 cloud adoption architecture.

Red Hat Summit 2021 (Ask the Experts) - An open approach to solution architectures (video)

This year the Red Hat Summit event is a bit different as we bridge the gap from pandemic reality to hopefully a form of normalcy. 

As the Red Hat Summit site explains to us, this "...event is expanding to become an all-new, flexible conference series, consisting of a 2‑part immersive virtual experience as well as a global tour of small-scale, in-person events. This series will create collective opportunities to share experiences, innovations, and insights."

Yesterday we presented our Ask the Expert session and the on-demand recording is available if you missed it. 

The event is free, so if you have not yet done so, register and you have full access to all the recordings. Now let's take a look at how to jump straight to our session

Cloud adoption - An architectural introduction

Part 1 - An architectural introduction

This article launches a new series exploring the cloud adoption 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 Architectural. 

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

Red Hat Summit 2021 (Ask the Experts) - An open approach to solution architectures

This year the Red Hat Summit event is a bit different as we bridge the gap from pandemic reality to hopefully a form of normalcy. 

As the Red Hat Summit site explains to us, this "...event is expanding to become an all-new, flexible conference series, consisting of a 2‑part immersive virtual experience as well as a global tour of small-scale, in-person* events. This series will create collective opportunities to share experiences, innovations, and insights."

Part one was from April 27-28, where you started your Red Hat Summit journey by joining us for this no-cost event, where you got the latest news, asked the experts your technology questions, heard from customers around the globe, and explored how open source is innovating the future of the enterprise. All of the sessions are online and available throughout the year on-demand.

Part two is from June 15-16, and you can build on what you learned at April’s event with insights from breakout sessions and technical content geared toward the tracks and topics most relevant to your career. You can also interact live with Red Hat professionals at this no-cost event. More depth at this event with the breakout sessions, ask the experts sessions, and a virtual expo hall.

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.