Project Status Inquiry: Roadmap and Maintenance State

[mvila]

Hi @tywalch and community,

First of all, huge thanks for creating ElectroDB. I've been exploring the documentation and the Single Table Design approach, and this library seems to be the most robust and developer-friendly option in the ecosystem.

I am currently evaluating the stack for a new production project and ElectroDB is my top choice. However, I noticed that the commit activity has been relatively quiet over the last few months.

Could you shed some light on the current state of the project?

1. Is ElectroDB considered "feature-complete" (stable) at this stage?
2. Is there a roadmap for future updates, or is the focus currently just on maintenance/bug fixes?

We are very keen to adopt it but just want to get a sense of the project's health and longevity before committing to it fully.

Thanks again for the hard work!

[zirkelc]

I'm not the maintainer, but active user of ElectroDB in a production deployment. In my opinion, ElectroDB is the best available ORM for DDB and very stable. The typescript support is amazing and the API reflects the current DDB capabilities.

[anatolzak]

Not a maintainer, just a user. We run ElectroDB in production with sustained traffic in the hundreds of thousands of RCU/WCU per second and it's been rock-solid. It covers all the DynamoDB stuff you don't really want to write by hand: transactions, condition expressions, GSIs, projections, hydration. The types are good enough that I actually trust the compiler when I'm restructuring access patterns, which was mostly why I picked it over rolling our own.

Full disclosure, I've also put up a bunch of PRs over time, mostly stability fixes plus a few small features, and they've all gotten reviewed and merged. So the quieter recent commit log doesn't worry me. Feels more like most of the obvious sharp edges are already smoothed than like the project's drifting. I'd pick it again for a new production project without thinking twice.