The Open Telekom Integration Platform is a complete and integrated suite of distributed, cloud-native and cloud-agnostic components for synchronous APIs, asynchronous messaging patterns and file transfer. It is an integral part of Telekom's architecture strategy.
The platform is modular in nature. It is currently in an early release stage. Thus, the key components are already available with many more to follow.
This repository contains the overarching documentation.
For the actual code, an overview of the available repositories is available here: Repositories.
This project has adopted the Contributor Covenant in version 2.1 as our code of conduct. Please see the details in our CODE_OF_CONDUCT.md. All contributors must abide by the code of conduct.
By participating in this project, you agree to abide by its Code of Conduct at all times.
This project follows the REUSE standard for software licensing. Each file contains copyright and license information, and license texts can be found in the ./LICENSES folder. For more information visit https://reuse.software/.
A comprehensive guide on how to get started with the installation of the Open Telekom Integration Platform is available here: Getting Started.
| Decoupling Done Right | Custom Open Source | Secure By Design |
|---|---|---|
| The Open Telekom Integration Platform's fundamentals are cloud-centric and API-first. It is a complete and integrated suite of distributed, cloud-native and cloud-agnostic components for synchronous APIs, asynchronous messaging patterns and file transfer. It is designed to be deployed on Kubernetes. | It is built based on top of open-source software, with all custom extensions capsuled in separate modules to remain product agnostic. | It provides secure and auditable access to APIs, with features like 4-eyes-principle, approval expiration, recertification, and more. |
| Declarative Configuration | Pipeline-Driven | Self-Service |
|---|---|---|
| The Open Telekom Integration Platform is configured declaratively, using YAML files. This allows for easy versioning, and the ability to use tools like Git to manage the configuration. You are just defining the desired state of the system, and the configuration tool (namely Rover) will take care of the rest. | Rover can run in a CICD-pipeline and is designed for that purpose. It enables the configuration to be integrated into a CICD-pipeline alongside the application code, and to be deployed together with it. | The Open Telekom Integration Platform is designed to be used by developers and operators alike. It provides a self-service eliminating the need for a central middleman. |
| API Management | Event-Driven Integration (Pub/Sub) | File Transfer |
|---|---|---|
| The Open Telekom Integration Platform supports the whole API lifecycle and allows seamless, cloud-independent integration of services. Further, it enables a fine-grained and vigilant API access control. The communication is secure by design, utilizing OAuth 2.0 and an integrated permission management. | The Open Telekom Integration Platform offers a component for asynchronous communication of services. It focuses on a resilient and loss-free event delivery, while maintaining high throughput volumes. Advanced filtering, payload validation and conditional delivery are also part of the feature set. | The Open Telekom Integration Platform enables large files to be shared between multiple services via the gateway mesh. It supports transfers and seamless end-to-end encryption of files without a size limit. |