Design and implementation of integration platforms. API and custom services development on integration projects. Performance testing and prophylaxis of integration platform.
System integration architecture and platforms
Integration interface development and projects
Integration performance testing
Prophylaxis of integration platform
Consultations and courses
Common data model
Integration approach, which brings the highest scope of flexibility and agility, gets its value mainly because of the DevOps possibilities, containerisation, and virtualisation/cloud. Basically distibuted approach to integration is a powerful tool, mostly in the parts of development and scalability, but on the other hand it lacks in the field of production and governance. To build a robust, fully operational, integration framework with the purpose of creating integration microservices is extremely costly in both, time and money. We are extremely proud to be a part of building and deployment of such frameworks in 2 big banking institutions, with the use of traditional server-based technologies Spring Boot and Camel, as well as serverless solutions Camel K.
More and more of our customers realize, that it's very efficient to exchange information between individual systems, not when the system needs them, but when the information undergoes and important change at it's source, so called "event". This event is then sent in a suitable manner and redisitributed among all the systems this event impacts. Sometimes this approach is also called "Streaming". The biggest advantages of this approach is the possibility to address the event with near-real-time reaction , the possibility to transfer huge amount of data, to work with the data on-the-fly and so on. To build this type of architecture we use technologies such as KAFKA, KAFKA Streams, kSQL DB, CONFLUENT, APACHE SPARK, Schema Registry, DEBEZIUM.
Nowadays, in our agile world is SOA considered a bit old school, but still it is a domineering approach to integration among big companies and corporates. Why is that? Simply, because often times a business case for a change doesn't exist, at the same time, this type of architecture, that has proven itself over the years among the users, many advantages. Among our customers, we take part on integration proprietary ESB platforms by ORACLE and IBM, or open source platforms, such as CAMEL and MULE. Another story is then "agilisation" of this, in its core "non-agile" approach of applicating automated DevOps practices.
The need of fast reactions to demands of front-end and mobile applications, increased security risks, single-sing-on, cost management of using integration services and a wide variety of factors resulted the creation of platforms such as API Gateway and API Management. Platforms, that, because of their nature, are most suitable for integration of front-end and mobile applications on internal system interfaces, are not only capable of replacing several components, that take care of integration security, but also replacing ESB, and all that while having higher support for the agile approach. Most frequently, we work with proprietary platforms by AXWAY and BROADCOM, or open-source platform MULE.
Call us to arrange a meeting