Solution
APIs and systems integration
Development of APIs and connectors between software, databases and external services. Message schemas, data transformation, call orchestration and retry handling.
Architecture and implementation
Interfaces and data contracts
Design of formats, schemas and interfaces for data exchange between applications.
Connectors and transformations
Adapters and processing pipelines for data conversion and distribution.
Events and orchestration
Coordination of real-time data exchange and scheduled processing.
Design decisions
Definition of API contracts, data mappings and retry mechanisms. Choosing synchronous calls, events or batch processing depends on acceptable application coupling and propagation delay.
Illustrative implementation
A change can be published as an event, transformed by a connector and applied once in the destination system despite repeated delivery attempts.
Engineering outputsExchange contracts, connectors, versioned schemas and retry mechanisms
In this shipment-tracking architecture, Android and iPhone applications send events to a command API. Kafka distributes them to consumers that update PostgreSQL views exposed through a read API. An analytical copy feeds Snowflake and Power BI for volume and lead-time analysis.
Docker
.NET
GitHub
JavaScript
Apache Kafka
Kotlin
Kubernetes
PostgreSQL
Power BI
Python
SAP
Snowflake
Swift
Components and flows
- Mobile and ERP events submitted to a .NET API with event identifiers and retry handling
- Kafka distribution, PostgreSQL projections and separate handling of failed events
- Tracking access through a read API; analytical copy in Snowflake and Power BI
A web and mobile application uses .NET services hosted on Azure, connected to PostgreSQL, Business Central and Microsoft 365. One example is a custom business portal for following quotations and orders, with access to related documents and records from the business management system.
Azure App Service
Azure Database for PostgreSQL
Business Central
.NET
Microsoft Entra ID
GitHub
Microsoft GraphJavaScript
Kotlin
Microsoft 365
n8n
Power BI
Terraform
Components and flows
- Web and mobile access to .NET application services, with Entra ID authentication
- n8n integrations with Business Central and Microsoft 365 through their APIs
- Azure App Service and PostgreSQL deployment, with private data access and Power BI publishing
A local gateway collects equipment measurements and events, then a Kafka and Spark platform combines them with SAP data for applications and analytics. One example is a production line whose current state is available through an application, alongside analysis of its production and quality history.
Docker
.NET
GitHub
Apache Kafka
Kotlin
Linux
PostgreSQL
Power BI
Python
SAP
Snowflake
Apache Spark
Terraform
Components and flows
- Equipment data read by a Python gateway on Linux; transmission to Kafka through a controlled network interface
- Spark time series processing and loading into PostgreSQL and Snowflake
- Enrichment with SAP data, .NET applications and Power BI analytics
Development and integration
- REST APIs, web services and exchange files
- Data transformation and synchronisation
- Event processing and message queues
- Integration services and observability
Systems involved
- ERP, CRM and business applications
- Databases, warehouses and data platforms
- SaaS, cloud services and partners
Service lineApplications and integration →
Services by sector
Explore the engineering services offered across different sectors.
Banking and insurance
Market feeds and financial reference data
Ingestion pipelines for prices, instrument reference data and corporate actions. Identifier mapping, update processing and validation of units, currencies and dates before distribution to databases and calculation services.
Energy and utilities
Measurement and market-feed collection
Connectors for provider APIs, files and event feeds. Series identification, unit and interval checks, historical backfill and integration of corrections published after initial receipt.
Logistics and supply chain
Transport APIs and events
Connectors for carrier events, tracking platforms and partner systems. Identifier, duplicate and timestamp checks, followed by status delivery through APIs or notifications.
Manufacturing
Industrial acquisition and interfaces
Connectors for equipment interfaces, including OPC UA where available, and production systems. Units, timestamps and quality states are preserved, with logging and collection-interruption handling.
Retail and e-commerce
Orders, payments and delivery
Integration of payment, order and carrier APIs. Server-notification processing and identifier reconciliation account for captures, refunds, shipments and returns.
To go deeper

A data platform for analytics, applications and AI
Data models, history and publishing interfaces that connect a data warehouse to analytical queries, applications and predictive models.

Defining the exchange contract between APIs and events
Transactional publishing, retries and message-schema evolution between an order application and its read projections.
Discuss your project
A discussion of your project’s design, development and production deployment.