This is the sixth blog in a series of 6 blogs about integration 2.0. Did you miss one blog, read the fifth blog Services!
The API- and Event hub may support most of the integration needs. Certain data however may require a specific approach, for instance if the size, speed or format of data requires this, or an external party demands it.
Though Integration 2.0 does not explicitly mention Services or Service Oriented Architecture (SOA) it makes a clear distinction between stateful services -services that maintain specific data – and stateless services that don’t.
Wij zijn nu sinds een aantal maanden partner van Studievereniging Sticky en voor het eerst aanwezig bij de Masterborrel. De avond werd georganiseerd om de bedrijven en de studenten met elkaar in contact te brengen. Tijdens de borrel hebben wij kennis gemaakt met de studenten van de opleiding informatica en informatiekunde. Het was hen erg leuk om onze kennis en de mogelijkheden die er zijn binnen SynTouch te bespreken. Het was een gezellige en zeer geslaagde avond!
The Event and API hub are the central components in the integration landscape: In principle all communication will go through them. Besides loosely coupling EAC-s and processes it connects with other generic IT capabilities (functions) as well, like Master Data Management (MDM), Reference Data Management (RDM), Business Rule Management (BRM), Identity and Access Management (IAM) and Audit and Compliance Management. These all may provide functionality or data required by processes, EAC-s or each other. However, these services and EAC-s themselves are passive components other than publishing events that might be listened to by other components.
This is the second blog in a series of 6 blogs about integration 2.0. Read the first blog Integration 2.0!
These recent developments have urged us to define a new Integration approach, that we call “Integration 2.0”. This approach aims to address the challenges posed by the technical and business developments for the next decade.
One of the best soundbites I read during the week of re:Invent, was on the t-shirts of one of the vendors right there … (see the title of this section). I cannot recall which one it was and I must confess that I just put all my summer clothing in storage. Anyway, going serverless is one of the big trends and for me, as an integration consultant, this is the most natural fit for moving into the cloud,
In the first part of my blog I commented on Las Vegas itself and my experiences travelling to Las Vegas; in this part I will describe my experience with the actual reason for travelling to Las Vegas, viz. attending the AWS re:Invent 2018 event.
As you may already know, re:Invent is the yearly conference from Amazon Web Services (AWS), this time its seventh edition, held in Las Vegas, for customers, partners and vendors from the AWS ecosystem. The size of re:Invent is astonishing, during this conference (starting on Monday and ending around noon on Friday), it welcomes 53,000 participans, spread across 7 different venues for a total of over 2,200 sessions of content.
This weekend I have returned from visiting my first AWS re:Invent. This seventh edition was (as always) held in Las Vegas – aka Sin City as it caters for the many vices people may pursue. Needless to say I have been a good boy and only indulged into drinking a few beers …
Digital disruption asks for new priorities in ICT-strategy. From killer app to killer data – this is how to start:
This blog is a new view to my earlier presented Data Value Chain-model. Data is an enterprise asset which represents value. The Data Value Chain visualizes and puts all data assets in sequence of increasing value. It is intended as a communication-tool to position our services and explain the opportunities and challenges of a data-related landscape.
Harald van der WeelSynTouch Data Value Chain – Reference Model