EventStoreDB

Showing 46 of 57

Delete streams without a trace

Customers who actively clean up their database encounter a situation when the scavenge.db file grows uncontrollably because it keeps the information about stuff that has been deleted. Eventually, it might lead to a situation when the scavenge.db f...

Alexey Zimarev 8 months ago in EventStoreDB / Operations 2

4 VOTE

Adjust the Log levels

At the moment the default log level is Debug, because lots of important logging is currently at the debug level. Users understandably sometimes raise the level to Information and miss important logs We should review and adjust the log levels of al...

Tim Coleman 3 months ago in EventStoreDB / Operations 0

3 VOTE

Support plugin configuration in the main yaml config

At the moment plugins can be configured via command line, environment variables, or json configuration file. But they cannot be configured in the main server yaml config. I think this is just because our yaml config parser only parses the top leve...

Timothy Coleman 14 days ago in EventStoreDB / Configuration 1

3 VOTE

Consider adding projection execution time to the metrics endpoint

Is it possible to add a new metrics for projection execution time?

Cindy Lo Min Chung 2 months ago in EventStoreDB / Operations 0

3 VOTE

Filtered reads and subscriptions to streams

ESDB currently allows filtered subscriptions to $all. The idea is to support filtered reads from $all, from streams, as well as filtered catch-up subscriptions to streams.

Alexey Zimarev 8 months ago in EventStoreDB / Dev experience 1

3 VOTE

Projections next-gen

Move custom and standard projections to Connectors.

Alexey Zimarev 8 months ago in EventStoreDB / Performance / Stability 0 Planned

3 VOTE

Server-side read models

It would be cool if we could take the users code and run it 'serverside' (meaning, in the nodes or in sidecars) the read models could be in memory, or persisted in one of a small selection of built in stores (stream store, kv store, relational sto...

Tim Coleman 8 months ago in EventStoreDB 0

2 VOTE

Consistency policies

One of the main concerns developers have about impoementing Event Sourcing is so-called "eventual consistency". It means that when a system implements one or more query models either in ESDB using custom projections or in other databases using cat...

Alexey Zimarev 9 days ago in EventStoreDB / Dev experience 0

2 VOTE

Remove the PLUGINS__ configuration section

The users don't need to know or care whether what they are configuration is a plugin or not. e.g. Instead of EVENTSTORE__PLUGINS__AUTOSCAVENGE__ENABLED we could have EVENTSTORE__AUTOSCAVENGE__ENABLED The tradeoff (and the reason why it is like thi...

Timothy Coleman 14 days ago in EventStoreDB / Configuration 0

2 VOTE

Timestamp-based reads

For temporal and bi-temporal models it would be beneficial to be able to read streams, as well as start subscriptions, using timestamps instead of positions. It would allow answering questions "what happened after that date and time, before this d...

Alexey Zimarev 15 days ago in EventStoreDB / Dev experience 0

Please enter your email address

FILTER BY CATEGORY