Your Partner for IT Integration

Industry 4.0, SOA, microservices, IoT, Big Data or digitalization – all these trends are increasing the exchange of data between software systems. Yet, what kind of information exchange will prove sustainable? With regard to all questions of IT integration, ConSol is your partner with many years of experience.

You do not have a precise idea of what your integration architecture should look like? For quickly achieving your objectives, you might use our blueprint. We recommend a microservice architecture with open source tools like Spring Boot, Apache Camel, Freemarker, Kafka, Artemis, or Zookeeper – all cloud native of course.

ConSol Integration Packages

Over time, various processes and areas of responsibility within a company often result in a number of separate IT systems and applications, appearing at first to have nothing in common. Maybe, a company for financial reasons selectively acquired individual components just as needed.

Using the ConSol integration packages Basic, Plus or Premium, your single solutions will act like as a whole.

We link your systems and independent tools in a way that makes your IT infrastructure work faster and more economically. We increase productivity and collect all data, thereby facilitating precise business analyses and ensuring your company’s competitiveness.

Keeping An Eye on Every Detail

Before an architecture can be operated successfully, numerous technical aspects must be clarified during requirements analysis and consistently implemented with up-to-date technologies. If you fail to see only one of the following details, the entire integration project might fail. Therefore, the design of ConSol’s solution architecture covers all these questions and services entirely.


Available Interfaces

Which interfaces do the systems to be integrated offer? Can information be pushed or does it have to be polled?


Message Format(s)

How do the messages to be exchanged look like? XML, JSON, plaintext, binary data, or proprietary protocols? Is message transformation from one format to another necessary?



To which target system is data forwarded? Is the routing static or dynamic based on the message content?



What are the requirements? Is the communication encrypted? How is the sender authenticated? Is authorization necessary? Do incoming and outgoing messages need to be signed?


Dealing with Errors

Which error scenarios can occur in the systems involved and if errors occur, how should the system react? How are network problems handled? Should automatisms such as retries be used?


Network Topology

Are the systems located in the same or in different network zones? Which elements e.g. firewalls, routers, load balancers, proxies etc. are involved in the communication?



What are the requirements in terms of message size, total data volume, capacity, and latency?


Specification and Documentation

What is the scope of an interface specification – depending on the technology used? What does a perfect and maintainable documentation look like?


Central Middleware Software

Is a point-to-point connection with adjustments in the source or target system sufficient or is a central integration platform necessary? In case of the latter, is an integration product (e.g. ESB) or a lean individual solution recommended?



Are interfaces continuously maintained? Can source and target systems always be installed parallelly in production or are all versions always downward compatible? Which other solutions do exist?


Maintenance and Operation

Which know-how is necessary for the later operation and support? Are there requirements with regard to monitoring, alerting and troubleshooting error scenarios?



Do messages have to be recorded individually? How easily can they be tracked throughout the overall architecture? Are statistics related to desired KPIs?

Most Important Technologies Compared

Messaging, SOAP and REST web services – these are the methods we usually choose, depending on the application. The following table illustrates their strengths and weaknesses.

 SOAP Web ServicesREST Web ServicesMessaging
Message FormatNative only XMLXML, JSON, PlaintextXML, JSON, plaintext, binary data
Routing1-to-1 synchronous communication only1-to-1 synchronous communication onlySynchronous and asynchronous 1-to-1 communication possible
SecurityTLS, basic and digest authentication, WSSTLS, basic and digest authentication, JWTMostly native
Network TopologyStandard HTTP(S)Standard HTTP(S)Special protocols and ports (e.g. JWS)
PerformancePerformance-intensiveLittle performance overheadMaximum capacity (if asynchronous)
Specification / DocumentationDefined specification language (WSDL)Non-binding standardsNo specification syntax specified
SoftwareWeb server with SOAP endpointsStandard web server is sufficientCentral broker and client libraries required
Maintenance and OperationHTTP and XML know-how is sufficientHTTP and XML know-how is sufficientProduct specialists needed

Project Profiles

ConSol stands for technological excellence and practical expertise. We draw on three decades of cross-industry project experience – in medium-sized companies as well as in DAX corporations and with other heavyweights. We support you in important software architecture decisions and place your solution on a solid, future-proof foundation.

Branch: Automotive

Project content: Application for market research and sales forecasting of automotive components.
Technologies: React, SpringBoot, MSSQL

Branch: Authority

Project content: Customer portal in a modern design for the provision of services for private persons and companies.
Technologies: Angular, SpringBoot

Branch: IT

Project content: Administration GUI for an Enterprise Cloud Software.
Technologies: React

Branch: Automotive

Project content: B2B application for the detailed comparison of vehicles and their equipment features.
Technologies: Angular, JavaEE, MongoDB

Branche: Telecommunications

Project content: Classic customer self-care portal for a telecommunications provider.
Technologies: Backbone.js, SpringBoot, JWT

Branch: Authority

Project content: Customer management for a municipal authority.
Technologies: Angular, Grails, ConSol CM

Branch: Automotive

Project content: Administration GUI for an application for provisioning vehicles.
Technologies: Angular, JavaEE, Microservice

Branch: Telecommunications

Project content: Application for market research and sales forecasting of automotive components.
Technologies: Microservice, Spring, REST, SOAP, Citrus

Branch: Telecommunications

Project content: Development of an integration platform for the exchange of Smart Meter data with SAP.
Technologies: Weblogic, SpringIntegration, SOAP, Messaging, Citrus

Branch: Automotive

Project content: Online interfaces for the provisioning of new vehicles
Technologies: Microservice, REST, MQTT

Branch: Automotive

Project content: Gateway for the internet communication of vehicles
Technologies: Microservice, REST, SOAP, MQTT, Citrus

Branch: Telecommunications

Project content: Web-based mail and messaging platform
Technologies: SOAP, Messaging, SMS, Citrus

Branch: Telecommunications

Project content: Online interface for data exchange with telecommunication providers
Technologies: SOAP, Spring, Citrus

Branch: Retail
Solution: Business service and system monitoring based on Nagios

Bpbb Deutsche Pfandbriefbank
Branch: Finances
Solution: End-to-end application monitoring with Sakuli

Bit@M, central IT service provider for the City of Munich
Branch: Public Administration
Solution: Open Source Monitoring with OMD

Branch: Telecommunications
Solution: Future-proof monitoring on Nagios basis

BStatutory Health Insurance Association of Lower Saxony
Branch: Public Administration
Solution: Seamless IT monitoring of the server landscape

Branch: Automotive

Project content: Advancement and transition to AWS of containerized microservices for processing vehicle data
Technologies: Java, Spring Boot, Java EE, OpenShift, AWS, Kubernetes, Terraform, Ansible, Citrus, PostgreSQL, Oracle Database

Branch: Automotive

Project content: New development of a scalable API gateway and caching services as containerized microservice
Technologies: Java, Spring Boot, OpenShift, Redis

Branch: Automotive

Project content: New development of containerised microservices for usage-based service contracts
Technologies: Java, Java EE, OpenShift, Citrus, TypeScript, Angular, PostgreSQL

Branch: Automotive

Project content: New development of containerised microservices for vehicle allocation
Technologies: Java, Java EE, Spring Boot, OpenShift, PostgreSQL

Branch: Automotive

Project content: Reference implementation for Big Data software projects for operation on a container cluster
Technologies: Apache Spark, OpenShift, Apache Kafka, Citrus

Branch: Automotive

Project content: Self-developed standard solution for backups of persistent volumes in container clusters
Technologies: Java, Spring, OpenShift, Restic, Citrus

Branch: Construction

Project content: Cloud-supported multi-client system for a SaaS software for quality management
Technologies: AWS, Kubernetes, Java, Keycloak, Terraform, Ansible, Gitlab CI, Citrus, Sakuli

Complex Requirements – ConSol knows the Answers

IT Integration: Technologies & Competences

Apache Camel
Apache Kafka
Apache ZooKeeper

We share our know how. Read more on our open source blog!


Christian Wied