Architect Consultant blog

Event Driven Architecture Event Driven Architectures (EDA) zijn hot. Ik denk mede door de populariteit van Microservices, want een EDA bestaat natuurlijk al veel langer. Zoals gebruikelijk in IT land doen ook hier weer een heleboel termen de ronde. Ik gebruik voor mezelf dan altijd een mindmap om alles een plekje te geven in het EDA landschap. Een EDA kun je hebben op verschillende nivo's: Binnen een applicatie component (bv Reactive) Binnen een applicatie (en dit is vaak wat je leest nu met Microservices en serverless) Tussen applicaties Tussen bedrijven (B2B) Tussen bedrijven naar klanten (B2C) Ik vind als integratie consultant vooral de laatste 3 vormen interessant. Ik wil deze mindmap hieronder graag met je delen en alle feedback is welkom natuurlijk.

One of my hobbies is photography and when I bought my first camera it was a compact camera. I soon realized and experienced that I needed a reflex camera (SLR), because the resolution, speed and quality was far more better. I did not realize it until I really used the product. Again after a few years I noticed that I did not use my camera a lot. Why was that? Because the camera was pretty big and unpractical to take with me all the time. Then I read about a system camera, which has the advantage of being small, but you still have the possibility to switch lenses. I never regretted my choices, because at the time it seemed to be the best choice. Today there are a lot of camera’s with a lot of possibilities and specifications. Which one to pick? It depends on a lot of factors and what you want todo with the camera, like portret-, landscape-, sport- and street photography. The same holds when selecting a software application, in this case an API manager. In my opinion there ...

"The flying Dutchman" (see also  photo page ) Key Takeaways Event Driven Architecture helps with decoupling applications Think about the names used for events Let Publisher publish and filter within subscribers Use meta data within event headers Use standardization on entities within Event, so that the Event is a first citizen data object Introduction 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 ...

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

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. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...