Added functionality to configure external databases for event storage #125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces the ability to configure an external database for storing events. The configuration can be done via environment variables, allowing the use of different types of databases such as MongoDB, PostgreSQL, or MySQL.
By default, all events are stored in a local in-memory storage. However, with this update, users can now opt to use an external database by setting the
PERSISTENCE_DRIVER
environment variable todatabase
ormongodb
and providing the necessary database connection details.Database
MongoDB
This enhancement provides more flexibility in terms of data persistence and storage options for events."