📄️ Architecture
Overview
📄️ Topic Structure
The topic structure is made up of the following four parts:
📄️ Serialization
KeySquare can operate with a number of serialization formats (see below). It natively uses SBE (Simple Binary Encoding).
📄️ Message Structure
All messages have a consistent structure defined as follows:
📄️ Monitoring
The KeySquare platform has been built with monitoring at its core. To that end, KeySquare ships a Grafana instance backed by QuestDB as part of the default stack. KeySquare can be reconfigured to output our telemetry to a different endpoint should you have a preexisting setup that you would like integrated. Please speak to your friendly KeySquare rep should you want to do this.
📄️ Message Caching
Messages published on the platform are cached by default.
📄️ Platform Best Practices
The KeySquare Platform can be run in a number of configurations depending on your performance requirements. This is really a tradeoff between hardware resources and performance.
📄️ Resilience
Platform Resilience