 |
| As seen online at KieLive episode #14 |
The goal of this guide is to provide you with a learning path through this content as a way to get started from download, to installation, to quick starts, to hands-on workshops, and all the way to using this technology for your cloud-native development projects.
You'll walk away from this guide with a learning path mapped out through content that's enjoyable to work with and can help you get started on your rules and process automation projects today.
 |
| My tenure: 2009-2022 |
How about a short summary of some of the highlights while at Red Hat before I move on to a new adventure?
I'll try to capture the big milestones, but there are just so many that I'm sure to miss a few.
It's a moment of reflection on more than a decade spent in the world of enterprise open source technologies and riding a wave that was Red Hat in the prime of its evolution in the industry.
I have been involved in open source since my introduction late in life to programming, operating systems, and Linux in 1996. Before joining Red Hat I was involved in the community around a business process management project called jBPM. We were using this heavily in the financial institution I was working at and I became active as you do when you submerge yourself into an open source technology.
As the official site says, Tuesday 10th May we have a special meeting of the London OpenShift User Group featuring:
Below you'll find the slides from my talk.
 |
| Figure 1: The portfolio architecture process |
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.
|
| Figure 1: The portfolio architecture process |
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.
|
| Figure 1: The portfolio architecture process |
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.
|
| Figure 1: The portfolio architecture process |
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.
I've mentioned previously that I had a talk accepted to the DevOpsDays Raleigh 2022 conference this year.
Today was the day after travel to Raleigh that we got to chat with a room of super enthusiastic architects.
Thanks for the time and lending us your ears. Below you'll find the talk title and abstract along with the slides for your viewing pleasure.
|
| Figure 1: The portfolio architecture process |
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.
|
| Figure 1: The portfolio architecture process |
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.
|
| Figure 1: The portfolio architecture process |
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.
The Devoxx series is well know and I've attended and spoken at multiple sessions for the Belgian version in the past. It's very developer centric with a lot of good depth and knowledgable attendees.
The selection committee decided that the workshop I submitted would fit their developer tools and productivity theme nicely so I'll be sharing this great material with you in London.
I've mentioned previously that I was trying to join the DevOpsDays Raleigh 2022 conference this year, to be hosted on April 13-14 in Raleigh, NC.
I submitted a few talks, a workshop, and crossed my fingers to await the selection committee results.
The verdict is in, I've got a session talking architecture shop selected. It's going to be fun to share my teams research and development of open source DevOps architectures.
Here's the talk and abstract and really looking forward to seeing you all in person!
It's been some years since I've been to this conference, mostly due to the worldly situation and travel restrictions, but thought this year was a great time to jump back in.
The 2022 edition will be held on April 13-14 in Raleigh, NC. You can register for tickets and join the fun for a really interesting array of talks and workshops.
I'm going to give it a good shot this year and have submitted two sessions and a workshop.
 |
| 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.
This year with hopes of attending some events in person, I've pushed a few talks to the Devoxx UK 2022 conference being held from 11-13 of May in London.
This is a rather close location for travel for me so seemed like a good one to put on my Spring list of conferences to target.
The Devoxx series is well know and I've attended and spoken at multiple sessions for the Belgian version in the past. It's very developer centric with a lot of good depth and knowledgable attendees.
My submissions are diverse and across the board as far as technical depth, architectural coverage, and type of sessions.
|
| 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.
|
| 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.
It's that time of year again when we get the Red Hat Summit 2022 call for papers!
I heard the call and thought this year would be a perfect time to go all in with sessions around our architectures based on a series of talks we've designed to showcase the various aspects we cover. Some are vertical aligned and others are just customer domains, but all of them include extensive research into how to implement successful architectures at scale.
Last week the call for papers closed and the internal committees are starting to churn through all of the excellent content they've been given. Sometime in March 2022 we should hear back from them.
How about a look at the various sessions we've put together where I'll be presenting with my good friends in the architecture team?
|
| 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.