Doorgaan naar hoofdcontent

Moving away from file interfaces

In the company I work for, I see a lot of batch oriented, file interfaces. An example is within the proces of where an employee gets employed.
This new employee ie entered within the PeopleSoft system and once a day an export is ran of all employees. This file contains the action that has to be taken towards other systems (add, delete, update). The other systems are phonebook system and authorisation system in which the new employee must be registered too. There is even a separate database that keeps track of the files already processed!

This is not what you want, but how would you integrate the systems? Should you use an ESB? Should you use a Common Data Model? Should you include BPM? Should you add another presentation layer?



All this creates a lot of overhead for a secondary process, just to SOAlize/BPM it. So what are the benefits to use this elegant IT solution?

I think:
* Monitoring of the process, so better maintenance
* Easier to change the process (for example other authorisation levels for different employees)
* Easier to change an implementation for a system
* Realtime update of the employee information instead of waiting a day or more

What's your experience in these kind of situations?
Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"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 .
47 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen