Error recording and publishing – any errors generated by a service are captured and recorded and can be surfaced in a custom UI or monitoring tools.If a service is down, or any of its dependencies are down, the heartbeating capability notifies other services, and anything else that is interested e.g. Heartbeating – this is aware of the services topology and runs in the background sending heartbeats and listening to responses.These features come “for free” with the framework and the developer simply has to enable them, and the Chronicle Services IoC framework takes care of everything else.Īs this article is focused on monitoring and observability, the features that help with this are: These services are configured in a simple YAML file – see extract below which represents the service highlighted in the diagram: position: FeaturesĬhronicle Services comes with a number of features to reduce the burden on the application developer. Each service has exactly one output queue, and one or more input queues. In the above generated diagram, you can see services (boxes), queues (cylinders), and the connections between components are labelled with message types, some of which have been excluded for clarity. The position server is also fed with execution reports from the FixTrading service, and sends position changes to the Pricer and the Hedger. This Chronicle Services demo application simulates a real use case – a basic market making system it generates random price ticks and sends them to the Chronicle EFX aggregator, which sends aggregated books to the Pricer and mid-rates to the Position Server. These services are a mix of pre-built services (from Chronicle EFX ) and custom built. it requires no effort from the application developer, other than to turn it on.Ĭhronicle Services also provides features that take care of the hard stuff: low latency, HA/DR, determinism, state management and restart, allowing the developer to concentrate on their area of expertise – the business logic.īelow is an example graph of a mesh of interconnected services generated with the services visualisation tool. Monitoring and observability is a first class feature of the framework, and comes “for free” i.e. Equally important they provide exceptional high-throughput and low latency. Microservices built with Chronicle Services are efficient, easy to build, test, and maintain.
Chronicle Services is a framework for building Event-driven microservices.
0 kommentar(er)
