 Good morning everybody and welcome to the DevConf presentation talking architecture shop with anyone. We're going to be looking at open source success at scale through a project that the portfolio architects at Red Hat, where I am also one of Eric D. Chabelle, the technical director of our products that we create. And what we'd like to do is collect some of the actual customer implementations and then take those to a generic level and share them with the world. So let's see what open source success at scale looks like. So in the beginning, when you start with architecture, one of the things you have is a plan, right? A very nice plan and usually everybody draws this up with great detail. It means we should end up with all the same exact execution, right? But when reality takes over and somebody else takes those plans and starts implementing, you could end up with something like this. Now I know this is a super extreme example and anybody with common sense you would think would not do something like this. But funny enough, sometimes our stuff ends up looking like this. So how do we get to a point in time where we can take plans that look really good and everybody implements them correctly? My idea and the idea of our entire team has been let's take a look at really good examples where people have done this and created really beautiful things. And if you could take all this information and share it in some kind of condensed form, this should help us map our solutions also to the same results. So what we've done is we've taken an architectural process, we put it together, trying to make it common and repeatable. And we have a visual language and tool sets, we have presentations, diagrams. We put quite a bit of stuff together over the last three, four years and you're going to get to see the results of this today. Some of the stuff that I put in the abstract for this talk has to do with retail. So we're going to cover three retail cases and I'm going to give you one extra one. Now each one of these cases that we decide to implement in this process has to do with three or more open source technologies. Now in our case at Red Hat we'd really like to see our products in there, but it could be three or more open source technologies. And that basically puts together a rather advanced integration of some kind of solution space, be that point of sales, be that real-time stock control, things like that. We have 24 or 25 of these and what it consists of is we've sat down and done customer research behind two to three implementations. Take those to a generic level and try to create diagrams. You see here an example of the architecture on the left and then we'll have three diagram levels from logical to schematic or physical and then a detailed diagram. Today we'll look at some of the market textures, the logical and few of the schematic ones behind each one of these architectures we're going to talk about. The field inside of Red Hat is given enablement and presentations around this. We have a public facing presentation includes some of the diagrams you're going to see today. At the end I'll provide some links to some of the public facing content so you can go explore those yourself. We also write up either articles or solution briefs that you can find on redhat.com. The publications tend to be spread around in different places. We do some of the stuff at Enable Architect. Sometimes they land on Red Hat property itself. Sometimes they're out on Dezo. You have presentation videos we'd like to put together which is sort of a process of walking through one of the use cases and all the content that's available and how to talk to that. You're going to get a little bit of that today. Where possible, where it exists, we don't build them generally speaking. It goes a little bit too far in our architectural product. But we do have within Red Hat various demos or in the communities around these open source technologies that might cover aspects of an architecture. In that case we will include those links so you can go explore that yourself. The first one up is supply chain integration and you're looking at one of the market texture diagrams. This is a high level introduction. Anybody can talk to this. It's really nice for these kind of presentations where you can say, hey, we're talking about these business drivers that has to do with supply chain integration. In the retail space in this case, it doesn't necessarily have to be confined to retail. And then you have a look at the container platform and some of the generic elements that are involved. It doesn't get too deep. It allows you to talk to somebody about what they're doing and where they're at and where they might be having problems. This then rolls over into the three levels of architectural diagrams and our tooling supports, where we've taken the time to do an open source tool as the basis. We started with draw.io and I believe it's called diagram.net now. And we put our own configuration on top of it to include some of the colors and icons that you see here that are brand approved for our company. It gives us a well-defined set that we can communicate with. You'll get a logical grouping and a logical view of what's going on in this architecture. You'll get a few schematical diagrams. Today we'll probably share just one in each one of the architectures, but there can be more based on what we find in the customer research. We try to document some of that at a generic level, not at the specific level of what happened to that customer. And then you'll have a detailed diagram or more of them. The idea being that you can talk at any level all the way down into zooming into these schematics to a specific component or element, I should say, which is a collection of components in one of these architectures. Again, back to supply chain integration. We have here groupings where you see the container platform that you saw. You see the elements involved inside that. You see the infrastructure services where they're located. You see the external systems there that are being connected to some of the storage services in this case. That we covered. And you see the hyper-cloud infrastructure. Nothing specific is talked about for a product or a technology or a community project. Nothing like that yet. It's all very much about a high logical level look at what's going on. Then we get into the schematic diagram where you see an actual case worked out where these elements you saw in the logical diagram are then applied. And you see a little bit more detail involved here now. So we have the various parties on the left side making some kind of a call in through API management. You'll note that one of these elements now includes reference to a product and implementation that could be used. It doesn't have to be, but we map as much as possible to these open source Red Hat products or just plain open source where it's not available as a product. We'd like to keep the open technologies sort of in the background, but it is a discussion that comes up when you start getting to how do you do that. So if you're somebody in an organization looking to do something around this supply chain integration, this is what successful customers have done at scale. So you have to look in your architecture and in your domains and decide event streaming, what choices have I made in the past, what am I been stuck with, or what am I using currently, or what am I open to using. And if it's Greenfield, we have a few suggestions. And you see that through the event streams various actions happen to integrate with back ends or with data frameworks, which is a separate architecture in itself, which we won't cover today. Another thing that's kind of nice about these and I'm going to drop out into out of the presentation and if you look in the speaker notes here at the bottom, I know it's a little bit small on your screen, but there's a link there. And that link takes us directly into, and I discard from my previous ones, takes us, that link takes us into the tooling itself where it opens up the actual diagrams and you see tabs here at the bottom. And the tabs include the various schematic logical and detailed diagrams and you can actually edit some of this stuff and you can manipulate this stuff and you'll see various aspects around the networking and whatever. You can put labels on things, you can change this to whatever your internal thing is for the customer you're going to talk about or to the architect you're talking about. You're also able to design your own should you want to. But this case, you're actually talking about discussing something with a slide and then jumping to everything we present is available to be manipulated and used. And on to the next one where we're talking about real-time stock control. So you see here that we have a container platform, we have the customer colleagues and supplier partners or vendors out there working through the various aspects of integrating with our stock systems. Finding out what's available to sell, keeping track of what's available to sell. Includes events that are being triggered to order management, supply chain systems, logistic systems, cataloging systems, catalog management, different things like that that might be important in your organization. Again on the left side the business drivers for this particular case. Very high level, very generic talk. Then you get into the logical diagrams again. Again you can open this up in the tooling, should you want to manipulate it for something else. We see here the external applications on the left, moving to the right, gateways and proxies, container platform with our various microservice and event streaming activities including process automation. And you see the infrastructure services on the back end that are indicative of possibly being external in the cloud or in the private cloud hosted on the retail vendor's own data center. Then we get to the schematics where real-time stock control. You see here the various actors on the outside there, various users and vendors and suppliers and colleagues and where they kind of plug into the various elements that are involved here that have API management handling, the requests coming in, generating events, maybe triggering processes that are a little bit more longer running, dealing with payments, promotions being generated and attached to various elements in our stock before we sell them, all the integration to the back end systems. Another comment that's worth being noted here is you'll see the colored lines are considered network connections. These are meant more along the lines of giving kind of a flow of what's talking to what, not identifying any kind of specific VPNs or certain network setups. That's left to the architects to figure out themselves. You will note that the dark black line there is connecting to a completely different side. We standardize that as being a data flow. So here you see the integration data microservices at the bottom that are connecting data in and out of the retail data framework which is an apart architecture. We have the omnichannel customer experience. Now, when you look back at the previous one, you'll see quite a bit of integration going on. So I thought I would mention we have almost 25 of these now, I believe, completely published and three or four more in progress. The omnichannel customer experience is one of them. I'm only showing you the introduction architecture story here. There's a whole portfolio architecture behind it with diagrams and everything. Feel free to go explore that when we get to the end. There'll be a reference slide that will show you a link where you can jump over and start looking at that stuff. I'll show you what that looks like in a minute. There are many more. So the final one I promised you in the abstract was the point of sale. Point of sale here has to do with sort of like a retail organization, developers in the top center there, deploying everything out to their image store. That's being spread around to the various retail locations. Where it's being pushed to the point of sale, whether it's apps or data collection or whatever it is. Those images are being updated and deployed as needed. And collecting from the endpoints of the various stores. We're finding sales data and feeding that back into our retail data framework so we can keep our stock control and that kind of stuff. Here's the logical diagram where we see on the left side the point of sales. The store server in the middle with the various aspects involved and elements involved there to make sure we're aggregating our sales data and collecting all that and keeping our catalog up to date. And then we have the infrastructure services that have to do with the developers on the back end through the point of sale, continuous integration and deployment platform where they're developing their images, their apps and pushing that out through the satellite server there. And here you see the schematic look at how that works where the schematic look, the point of sale where we see on the left side the developers and the operations and the retail data framework. And then you have the central retail IT where they're doing the development and setting up the images and the application to be pushed out to the individual retail stores. We're indicating multiple stores with those gray boxes layered like that showing you one store in specific here where the image and data store cache is being used to update the point of sales. Where the point of sales are also feeding in the sales data aggregation information to be able to send back so they can keep the skewed catalogs up to date and in sync from the retail data framework. More information here. I talked about the examples repository. We can go ahead and drop out of here and take a look at what that looks like. So this is over here. You'll see the retail is listed here. I can zoom this up a bit. The documentation is here. Retail, healthcare manufacturing, financial services, cloud adoption, hybrid cloud management. There's lots of these things in here. Let's take a quick look at the retail one. That'll be kind of, you see where you can load the diagrams. That's the same link you'll find in the slides. You can also just download the diagram file and use it to draw a tooling that you can install locally. See here the architecture and the various things that are involved within this case, the supply chain integration. So you can actually look at just the images and use those directly in your slides if you want. Point of sale, there's lots of these involved here. Headless e-commerce, business optimizers, more and more. We also have the workshop here. I wanted to jump over to that quick. So if you're trying to figure out how to use the tooling directly, the best way and the recommended way would be to go ahead and jump over here and take this designing your best architectural diagrams workshop. I'll do a little preview here in the menu and you see the various labs that you're walking through. We're exploring it and discovering what the asset library and the colors are for and how to connect and create logical diagrams, schematic diagrams, detailed diagrams, importing and exporting them so you can use them in your presentations and a few examples of how to use some of the quick starts and other tips we have. A little bit later today, here at the DevConf, I'm going to be doing a live workshop around this so feel free to join me there. If you can't make that, then this is online as you can see and you can do it at your own pace. So feel free to join me later. That's a shameless plug. Head back here to this. I would like to thank you. That brings us to the end here. Three different retail architectures, as promised in the abstract. I gave you a quick peek at the OmniChannel as an extra fourth one. We looked at the tooling, we looked at what it's constructed of, showed you a few places where you can find and get started if you want to do it yourself, invited you to my workshop later. So if there's any questions or any comments or any feedback you'd like to give, please drop into the chat and let me know. I'll be hanging out for a while anyway. You can also find me online. I'm not a stranger, so feel free to connect. Thank you.