Home

In Kozen, the modules are used as independent tools. The Triggers module becomes a solution designed to provide support for Self-Hosted Triggers in a simple way, whether you're using MongoDB Atlas, Enterprise Advanced, or Community Edition. This helps streamline the process of managing triggers across different MongoDB deployments.

📚 Self‑Hosted Triggers

Kozen can run MongoDB Change Stream based triggers on your own infrastructure. If you’ve used MongoDB Atlas Triggers, think of this as a self‑hosted alternative: you write a small JavaScript file (the delegate) that exports simple functions per operation, and Kozen wires everything up to stream change events into your code.

🎯 Overview

Atlas context: MongoDB Atlas provides a fully managed Triggers service. Kozen offers a similar capability you can run anywhere (local, on‑premises, cloud), while keeping your logic in a single, easy‑to‑maintain JS file.

Basic → Advanced overview:

• Basic: install Kozen, point to your .env, and use the example Delegate.
• Intermediate: learn how Kozen routes events and how to configure environment variables safely.
• Advanced: adopt best practices for idempotency, security, performance, and operations.

🚀 Quick checklist:

• Install Kozen.
• Write the delegate with insert/update/delete/replace and optional on/default.
• Fill .env with KOZEN_TRIGGER_* settings.
• Start the service and verify logs.

For better understanding, please read the 'Get Started' section

🧭 Where to go next

• Get going fast: Get Started
• Learn how handlers work: Delegate
• Configure everything via env vars: Config

📖 References

• Kozen Triggers through DeepWiki
• Disclaimer and Usage Policy
• How to Contribute to Kozen Ecosystem
• Official Kozen Documentation
• What are Database Triggers?
• MongoDB University
• MongoDB University: Intro to MongoDB Change Streams
• MongoDB Manual: Change Streams

---

← Previous: — | Next: Get Started →

---