Welcome to EnSync Engine!
EnSync Engine is a message delivery system aimed at enabling apps communicate natively and realtime with almost no friction.
Introduction to EnSync Engine
EnSync Engine provides sets of tools that enable apps that you integrate with send and receive events/messages in realtime as if they were native to your architecture.
What Makes Up EnSync Engine
At the moment, the engine comprises two major parts which includes:
- Config Manager
This part of the system powers the configuration and administration of the Engine. The config manager provides APIs which powers our CLI and are open to you for configuring and automating actions. It also provides GRPC services which are for internal use only.
- Node Engine
The node engine acts as the delivery system which enables authorised clients securely publish messages which gets delivered to other connected clients. This service also handles archiving messages and partitioning storage files within your server. Our client SDKs connect to this part of the engine to publish, subscribe, acknowledge, pull records and more.
Before we continue, we wanted to clarify a couple of buzz words you may occasionally find in this documentation.
Buzz Words
Events:
Notification that an action has occurred or a task has started, been updated or even completed.Messages:
An event with payload that may contain a header that is published by a system to update any listening service on progress of a task.
Myths about EnSync:
EnSync Engine can only be used for third-party event/message delivery.
You can't use EnSync Engine if you already have an event driven architecture.
Facts about EnSync:
EnSync Engine is a central message delivery system.
EnSync Engine can process thousands of messages per seconds.
EnSync Engine can be used to build event driven architecture for your internal apps.
EnSync Engine can