\n\n\n### Interested in Gallifrey-Rules?\n\nI offer free one to one sessions via Google Meet to kick-start adoption or to answer questions about the library. \nPlease reach out at `mail[at]gallifrey-rules.dev`\n\n### Features at a glance\n\n* **Structured Event-Driven Architecture (EDA)**: Enforces a disciplined approach to event-driven development, ensuring consistency and best practices across your projects.\n* Transform **Consumer Blackbox** => Modular design with Filters, Rules, DataObjects, and Actions as customizable plugins, enabling seamless extension and flexibility.\n* **Dynamic Plugin Management**: All modules, including plugins and providers, are dynamically loaded and referenced by name,\n* **Namespace-Oriented Projects**: Projects are organized into **Namespaces**, each consisting of a **Namespace Schema** and a list of modules, promoting modularity and reusability.\n* **Abstracted Configuration Management**: Configurations are managed through an abstracted provider, allowing them to be sourced from any backend, ensuring flexibility in various environments.\n* **Logging and Metrics**: Logging and metrics are abstracted behind providers, offering a consistent and extensible approach to monitoring and diagnostics. Out of the box support for [InfluxDB](https://www.influxdata.com/)/[Grafana](https://grafana.com/).\n* **Journal Logging**: Capturing/grouping high level logs that happen during a single event.\n* **Scheduled Events Support**: Native support for scheduling events in the future, with rules that can seamlessly trigger new events based on business logic.\n* **Distributed Locks**: Out-of-the-box support for distributed locks, enabling atomic event processing and ensuring data integrity across distributed systems.\n* **Asynchronous Actions**: Actions can be easily converted into Async Actions with dedicated consumer topics, allowing for efficient time management and workload distribution.\n* **Comprehensive Metrics Tracking**: Tracks counts and durations for each plugin type, enabling quick identification of performance bottlenecks, such as slow data pullers or actions.\n* **Enforced Naming Conventions**: Consistent naming conventions across the library, enhancing the developer experience and reducing the likelihood of errors.\n* **Resilient Error Handling**: The ReactToFailure mechanism is abstracted behind a provider, giving developers control over how to handle unexpected errors in a customizable and consistent manner.\n* Fully supports [TypeScript](https://www.typescriptlang.org/).","readmeFilename":"README.md"}
![\"Logo\"](\"https://raw.githubusercontent.com/ralphv/gallifrey-rules/main/docs/resources/gallifrey-rules-25.png\")
\n \n