An Event Driven Architecture is one that has the ability to detect events and react intelligently to them. An event is a state change, which draws the attention of systems and is evaluated by them to decide whether trigs or not an action. An example of an event-driven system is […]
EDA (Event Driven Architecture) Lees meer
With the mobile applications “boom”, and because they rarely are standalone, it came the necessity to create ways to the mobile applications incorporate access to external data and functionalities [1]. A Web API-base architecture is used when is necessary to integrate applications with websites or other applications. This architecture pattern made
Web API-gebaseerde architectuur Lees meer
There are several ways of implementing a SOA integration, but let us focus on two. Web Services Web services are the most common way to implement a SOA. They are based on protocols such as HTTP, FTP and SMTP. There are two main styles of web services, SOAP and REST.
Webdiensten en microdiensten Lees meer
SOA can be defined as an architecture which goal is to achieve decoupling among interacting software agents [1]. From the SOA point of view, systems expose their functionalities as a set of services, typically as a set of Web services. It does not matter which technology platform the system sits
SOA (Service Oriented Architecture) Lees meer
Message Brokers allow the information flow between applications. Following this type of middleware, we advance to an integration architecture that is based on message brokers. As the applications universe grows and the Point-to-Point architecture is no long a viable option, the necessity of middleware is obvious. One of the possible
Hub-and-Spoke Architectuur Lees meer
In the last chapter we introduced the notion of middleware, why we need it and how it turns integration easier. So today we are going to talk about the different types of middleware. And let us start with one vert used in point-to-point integration: RPCs (Remote Procedure Call) Middleware RPC
For years, information systems have been built as “stovepipes” [1], creating monolithic self-contained applications that have not been designed for integration with other applications. These systems were built with very specific requirements and not using standard data storage and application development methods [2]. However, even years after its implementation, they
Point-to-Point-architectuur Lees meer
Today’s applications integration is of great concern for organizations. Due to the large flow of existing information, an increasing specialization of the applications and the great speed at which it is necessary to implement the various requirements that allow organizations to continue to operate successfully, it became crucial to create
Integratiearchitecturen voor bedrijfsapplicaties Lees meer
In the next five to ten years the way people and businesses make decisions, may change dramatically. Data and the knowledge people can get from it will be the centre of this process. Unconceivable amounts of data will be produced by individuals, corporations or devices. Vendors and software will provide
De gevolgen van big data Lees verder
[et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row” background_position=”top_left” background_repeat=”repeat” background_size=”initial”][et_pb_column type=”4_4″][et_pb_text background_position=”top_left” background_repeat=”repeat” background_size=”initial” _builder_version=”3.19.10″] We have been using TIBCO BusinessWorks 6 for almost an year and felt that it’s time to share the reasons why you should care about it.TIBCO ActiveMatrix BusinessWorks™ 6.2 represents a great improvement in the number one integration platform,
Waarom moeten we upgraden naar TIBCO BusinessWorks 6 Lees meer