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.

Store health and safety - An architectural introduction

Part 1 - An architectural introduction

Welcome to 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.

Red Hat Summit 2021 - How to enjoy this three part event series

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 is from April 27-28, where you can start your Red Hat Summit journey by joining us for this no-cost event, where you can get the latest news, ask the experts your technology questions, hear from customers around the globe, and learn how open source is innovating the future of the enterprise. There will be keynotes, spotlights, live demos, and access to Red Hatters from around the globe.

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.

Finally, you noticed the star marking the part three event above? That's because this part of the event we hope allows us to meet in-person, but the ongoing situation means Red Hat will "...continue to monitor the ongoing global health crisis and make adjustments to the Red Hat Summit agenda to help ensure the health, safety, and well-being of everyone within the open source community."  If all goes well, then you can cap your Red Hat Summit experience somewhere from Oct - Nov "...by exploring hands-on activities at in-person events that will be held in several cities. The networking opportunities can help you find the inspiration to discover who you want to be and the tools to do what you want to do." There will be hands-on labs, 1-1 meetings, and training courses available during this final event series.

Headless eCommerce - Example headless architectures

Part 3 - Example headless architectures

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

Headless eCommerce - 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 headless e-commerce architecture.

Headless eCommerce - An architectural introduction

Part 1 - An architectural introduction

We're kicking off another series sharing a new 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.