Veel organisaties streven ernaar om “data-driven” te zijn. Dit heeft impact op de architectuur en organisatie van een bedrijf. Data werd altijd gezien als bijvangst, maar is tegenwoordig steeds belangrijker om goede beslissingen te kunnen nemen. De architectuur rondom data verandert ook qua mogelijkheden zoals data warehouse, data lakes en een nieuw paradigma genaamd data mesh. Deze blog geeft een introductie over dit data mesh concept en de impact op de architectuur en organisatie.
This is the second blog about event driven architecture. As was described in the first blog item, there are several levels on which events occur and are relevant. It is important on which level you want to implement your EDA. In this blog I will concentrate on the application-to-application level and beyond and I will describe a reference architecture that we use at SynTouch.
Events are the driving force within the event driven architecture. Events are produced, detected, consumed and reacted upon. One of the main principles of EDA is the separation and isolation of the sources and the handling of the event notifications. The advantages and use cases for an EDA are:
Data is the buzzword these days: organizations want to be data driven. They create a lot of data, want to create value out of this data and want the data fast and available 24/7. Therefore the IT architecture needs to be flexible, scalable, resilient, responsive and message (data) driven.
This is where an Event Driven Architecture (EDA) can help and in the next 4 blogs I want to guide you in this event journey.
This first blog will be about events in general and how they can be utilized on all kinds of levels within an organization. In the second blog I will talk about a reference architecture that organizations can use as a starting point. It explains which capabilities are relevant in such an architecture. In the third blog I will describe some principles and guidelines that you can use within an event driven architecture. In the last blog I will explain how an organization can become event driven. I will take you through a maturity model and the steps that you can take to get to a level that your organization needs to reach its business goals.
Op 15 november 2018 hebben we met SynTouch het Landelijk Architectuur Congres bezocht in de Brabanthallen in Den Bosch. Dit jaar was het thema “Paradoxen in Architectuur”. En dit jaar konden we een feestje vieren, want het LAC bestaat 20 jaar !
Normaal gesproken is het beeld van een architect saai, oubollig en werken vanuit een ivoren toren. Kijken of hier langzaam verandering in gaat komen en zelfs sexy gaat worden. Of blijkt dit toch nog steeds een paradox?
There is a lot of hype around Microservices and the use of events for implementing the choreography pattern. However this is nice for companies like Netflix and Twitter, but there are a lot of organisations still struggling with files and ESB like products. Also my current client uses an ESB namely the Oracle SOA Suite 12c for integrations. We cannot just throw away this ESB, but we can make use of the event mechanism built in. This blog describes the way we use the EDN (Event Delivery Network) component, that is used within SOA composites to throw events and to subscribe on events.
A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations.
On the 22 and 23rd of March I went to the ‘Microservices Conference 2018, MicroXchg’ in Berlin. This blog post is a short recap of my experience of this conference, this year held for the 4th time.
My goal was to learn more about the Microservices world, to fill my toolset of possible architecture solutions and of course to see Berlin a bit. Furthermore, I interviewed Chris Richardson about Microservices and his upcoming book on Patterns. This interview is added to this blog as well.
Veel productiebedrijven met productielocaties waar de producten daadwerkelijk gemaakt worden, hebben moeite om de business-systemen aan te sluiten op de productievloer-systemen. Op kantoor worden sales orders ontvangen. Deze worden doorgestuurd naar de planningsafdeling. En uiteindelijk worden de productieorders verstuurd naar de productievloer. Deze supplychain omvat dan plan-source-make-deliver.
