Architecture

Moneyhub's Categorisation & Enrichment Engine achieves its scale by running an internal Kafka deployment to move messages, containing transactions, between internal components, with each of those components processing multiple messages in parallel on multiple cores. We support different interfaces into our engine depending on your needs.

The API and SFTP interfaces pipe to and from our Kafka ingress and egress topics. From an outside perspective, the API interface presents as synchronous RESTful endpoints.

For the best sustained performance, we suggest a Kafka interface, especially for non-critical path pipelines. This interface can utilise Kafka Brokers hosted in either your infrastructure or ours. When using your infrastructure, the Categorisation & Enrichment Engine will be configured to consume from and produce to your topics. When using the Engine's Kafka, we will provide credentials that allow you to produce to and consume from our topics.

Moneyhub Categorisation & Enrichment Engine Architecture diagram

The architecture of the transaction categorisation and enrichment component of Moneyhub's Categorisation & Enrichment Engine