Our success formula: put leading edge technologies in the hands of smart people and give them the autonomy to get to work with them
Our Miles core solution server is developed in JEE7 on Java 8.
Additionally, we have a microservice platform based on Kubernetes on which our microservices are mainly built with the Java Quarkus.io framework but non-Java services (using e.g. Go) are also part of our delivery pipeline.
For front office point solutions (web portals, mobile apps...) we rely on various technologies: Google Web Toolkit, Angular, Flutter.
In recent years, we have expanded our Miles core solution with a next generation cloud-based services platform. This cloud-native microservices architecture enables modular feature delivery, 24/7 availability and elastic on-demand scalability with near real-time data integration and advanced analytics power.
The reference architecture is a particular set of technologies which are used to bring all the components to deploy, manage and monitor the deployment landscape. The microservices platform uses several components to establish its feature and functionality set, the following list illustrates which technologies are used within the reference implementation.
The 'API Manager' is a central component within the microservices platform , it is used to offer a unified service API to the outside world, expose service documentation and also acts as a governance layer to protect the service platform from unauthorized access and malicious use of services. As part of the reference architecture Sofico has selected Tyk.
The 'Identity Provider' is another key component in the architecture which closely integrates with the API Manager to provide authentication and authorization on the service level. As part of the reference architecture Sofico has selected Keycloak.
The 'Object Store' provider cloud native object(file) storage functionalities towards the microservices platform to make distributed file storage available to the services deployed onto the platform. As part of the reference architecture Sofico has selected Minio (S3 Compatible).
The 'Orchestration' layer of the reference architecture makes use of Kubernetes and has a very strong focus on CI/CD by using tools such as Jenkins, FluxCD & Helm Charts.
The 'Reverse Proxy' enables simplified internal networking inside the microservices platform and offers protection from the outside by limiting the amount of ports which need to be opened towards the service platform. As part of the reference architecture Sofico has selected Traefik.
The 'Log Management' components enable centralized logging and log analysis within the microservices platform. As part of the reference architecture Sofico has selected Elastic Stack.
The 'Monitoring' functionality allows in depth monitoring of all components involved in the microservices platform. As part of the reference architecture Sofico has selected Dynatrace.
The 'Queuing System' offers advanced parallel processing capabilities to the microservices platform. As part of the reference architecture Sofico has selected Kafka.
The 'Data Streaming' component which is closely linked to the queuing system enables fast data streaming between databases and data pipelines. As part of the reference architecture Sofico has selected HVR to be used.
Miles core can run on an application server (Websphere, JBoss, Weblogic) in combination with an Oracle or SQL Server database. It can also be packaged as container in which JBoss EAP 7 is used as an application server. These are supported on different platforms: Microsoft Windows Server, Red Hat Enterprise Linux Server (or CentOS), Suse Linux Enterprise or Sun Solaris.