 |
| 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.
 |
| 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.
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.
In this four part series you were familiarised with the OpenShift Container Platform, the business automation operators, and given a project to install the developer tooling needed to begin designing processes, rules, and much more.
Recently, there were updates to the CodeReady Containers offering that gives you the latest OpenShift Container Platform 4.9.10 to run quite easily on your local developer machine.
Time to update the various projects for leveraging to learn business automation tooling better known as the Red Hat Process Automation Manager and Red Hat Decision Manager. Along with these installation projects, you'll be able to use the free online workshops with the latests tooling.
In the previous article in this series, we introduced the world of Codeanywhere, a cloud IDE and container development experience all available in just your browser.
Are you ready for some more amazing, easy to use, developer tooling that requires not a single tooling installation and no configuration?
That's what the team at Codeanywhere are promising us when I stumbled on their website last week. They "...don't require you to engage in complex installations and configuration setups. Simply access our in-browser IDE for everything you need to build amazing websites in a productive and more developer-friendly way."
In part three of this series, we'll finish the setup of our process automation Java container project in Codeanywhere.
Recently the open source community project called Podman announced that there was solid support for using its container tooling to replace docker on your local development machine. Ring in the joyous music and off we go to explore how we can get back to basics without the issues of licensing around the developer desktop container tooling.
Note, the rest of this tutorial will be based on the current version of Podman at the time of publication, v3.3.1.
The first thing you want to do is just install the Podman tooling, which is fairly painless using BREW:
$ brew install podman
Now you are ready to kick off the virtual machine with the proper settings to start doing something real, like adding developer decision management tooling to your local machine.
Note, the rest of this tutorial will be based on the current version of Podman at the time of publication, v3.3.1.
The first thing you want to do is just install the Podman tooling, which is fairly painless using BREW:
$ brew install podman
Now you are ready to kick off the virtual machine with the proper settings to start doing something real, like adding developer process automation tooling to your local machine.
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.
 |
| Part 3 - Example data architecture |
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.
|
| 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.