Demystifying the Event Driven Architecture - An open solution (part 3)

High throughput, resiliency, scalability and speed—are you searching for a way to leverage microservice integration to handle all the event-driven communications in your growing architecture landscape?

Search no further.

This series of articles guides you through the world of integration using microservice architecture and specifically explores the world of Event Driven Architecture (EDA). It’s a central story to organizations moving forward into the digital world and is worth exploring as part of your strategy for continued success.

The first article was introducing how EDA might be the right choice for your microservice integration solutions, with a more detailed examination of when you might not need EDA at all. The second article pivoted back to exploring use cases aligning to EDA solutions and presenting real world examples. This last article looks at the open technologies that can help you to implement an EDA architecture.

Cloud-native development - On local containers

Part 3 - Development on local containers

The previous articles were introducing the foundations of an architecture for cloud-native development, starting with a logical diagram and its common architectural elements.

In this article we're continuing on to example use cases within the architecture. Descriptions are provided to guide you with aligning the landscape your organization works with every day.

These details should help you understand both what the elements contain and how they might align and how their functionalities are grouped. Let's look at the use case where developers are leveraging local container tooling for their cloud-native development environments and see how that's mapping to a productive working architecture for deploying their solutions.

Cloud-native development - Common architectural elements

Part 2 - Common architectural elements

The introduction for cloud-native development laid out groundwork for a deeper exploration of its logical diagram.

In this article we continue with a look at the common architectural elements. A description is provided to guide you with aligning what we've presented here with the landscape your organization works with every day.

These details should help you understand both what the elements contain and how they might align and how their functionalities are grouped.

Let's look at the foundation of our cloud-native development architecture, the logical diagram with it's architectural elements.

Speaking Bites: 5 Traits Putting Your Audiences to Sleep (slides + video)

Today we held an internal, yep, an internal only mini Red Hat Summit.

This is a chance for talks to be presented select content to an internal worldwide audience at Red Hat, but that does not mean that all the content is confidential. That means I would be remiss if I didn't share my session content.

In 2018 I presented a non-technical soft skill session to Red Hat associates about how to build and tell a story. This was a deviation from my normal technical subject matter, but after being on stages and in front of crowds for almost 10 years, it was time to share some simple tips to engaging audiences.

To say the least, this went over well and word travelled fast. I have since shared this storytelling session over three continents and with 13 (and counting) audiences. It's been recorded four times so far and continues to help others improve their effectiveness with engaging audiences of any size.

See below for this somewhat updated version and to access both the slides and a video recording of my presentation of the slides.

Reality Bites: 3 misconceptions that can lead to microservice mayhem (slides)

Today we held an internal, yep, an internal only mini Red Hat Summit.

This is a chance for talks to be presented select content to an internal worldwide audience at Red Hat, but that does not mean that all the content is confidential. That means I would be remiss if I didn't share my session content.

In 2019, together with Roel Hodzelmans, we presented a Red Hat Summit birds of a feather session called 3 pitfalls everyone should avoid with microservices. This was the foundational start to our journey along the lines of sharing what is concerning to many of our customers.

We explored some of the feedback from our session and continuing interactions with customers in the five part series 5 questions everyone is asking about microservices. Furthermore, some of the material led to the creation of two architectural blueprints around agile integration use cases:

• Omnichannel customer experience
• Integrate with SaaS applications

See below how this led to our reality bites session based on our article on InsideBigData.com and access both the slides and a video recording.

Cloud-native development - An architectural introduction

Part 1 - An introduction

After starting with architectures introducing both omnichannel integration and integrating with SaaS applications, we're presenting the results of a cloud-native development architecture.

What's in a portfolio architecture and what's the focus you ask?

It's an interesting challenge in that we've been 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 marketing chuff. 

These portfolio architectures are providing you with a way to implement a solution using open source technologies focusing on the integrations, structures and interactions proven to work. What's not included are any vendor stories that you'll find in normal marketing content. Those stories that when it gets down to implementation crunch time, might not fully deliver on their promises.

Let's look at the cloud-native development architecture and explore their value in helping your solution designs.

Demystifying the Event Driven Architecture - Making the case (part 2)

High throughput, resiliency, scalability and speed—are you searching for a way to leverage microservice integration to handle all the event-driven communications in your growing architecture landscape?

Search no further.

This series of articles guides you through the world of integration using microservice architecture and specifically explores the world of Event Driven Architecture (EDA). It’s a central story to organizations moving forward into the digital world and is worth exploring as part of your strategy for continued success.

The first article was introducing how EDA might be the right choice for your microservice integration solutions, with a more detailed examination of when you might not need EDA at all. This article pivots back to looking at use cases that align to using EDA solutions and presents a few real world examples. Lastly, we’ll look at the open technologies that can help you to implement an EDA architecture.

Code Ready Containers - Installing an HR employee rewards project using developer container catalog

If you've been following along here lately, you've noticed that I'm exploring Code Ready Containers quite a bit. I've been looking at how to run an OpenShift Container Platform, self-contained on my local machine with no more than 16GB of RAM.

It's not about just starting up the container platform, it's about doing something real with it. By real I am talking about running a demo, project, or some coding solution I enjoy tinkering with for my day job.

With that in mind, I've pulled together a project that installs Code Ready Containers for your local machine using 11 GB of RAM. That's the basic setup for running any of the subsequent projects I've shared with you in the past.

After that I've started sharing how to install various developer tools using the provided developer container catalog images; Red Hat Process Automation and Red Hat Decision Manager. Now it's time to look at installing real projects that allow you to explore the usage of the tooling.

Let's take a look at installing a human resources employee rewards project using the developer container catalog on Code Ready Containers.