Evgeny, Arjun, and Donna here - we’re building cloud-hosted data change tracking for PostgreSQL. We’re launching our first open-source integration for TypeORM that allows applications to automatically attach additional metadata to database changes. The repo is at https://github.com/BemiHQ/typeorm and our home page is https://bemi.io.
We used to all work together at a startup five years ago, and now have got the gang back together to go full-time on Bemi! We’ve built robust compliance engineering systems before, for example at AngelList, but only recently learned that the tech is useful to other companies. We’ve been following that demand to build a general-purpose tracking solution that can be used for a wide range of use cases such as audit trails, reverting changes made in an API request, testing different application states, etc..
We’ve built Bemi to be lightweight and secure. It takes a practical approach to achieving the benefits of event sourcing without requiring rearchitecting existing code, switching to highly specialized databases, or using unnecessary git-like data versioning abstractions. We want your system to work the way it already does with PostgreSQL to allow keeping things as simple as possible.
We plug in at both the database and application levels, to get reliability, performance, and also a comprehensive understanding of every change.
On the database level, we ingest changes using change data capture (CDC). On the application level, our library allows passing application context and metadata to the write-ahead logs (WAL) automatically. We then stitch the change data together and store it in a structured format in a destination cloud PostgreSQL.
We plan to charge for storage and compute if you’re a company storing >1M changes a month. We’re still early and it’d be amazing to get HN’s feedback.
What do you think HN?
0 comments
—
Show HN: Bemi for TypeORM – automatic data change tracking · HackerTrans
We used to all work together at a startup five years ago, and now have got the gang back together to go full-time on Bemi! We’ve built robust compliance engineering systems before, for example at AngelList, but only recently learned that the tech is useful to other companies. We’ve been following that demand to build a general-purpose tracking solution that can be used for a wide range of use cases such as audit trails, reverting changes made in an API request, testing different application states, etc..
We’ve built Bemi to be lightweight and secure. It takes a practical approach to achieving the benefits of event sourcing without requiring rearchitecting existing code, switching to highly specialized databases, or using unnecessary git-like data versioning abstractions. We want your system to work the way it already does with PostgreSQL to allow keeping things as simple as possible.
We plug in at both the database and application levels, to get reliability, performance, and also a comprehensive understanding of every change.
On the database level, we ingest changes using change data capture (CDC). On the application level, our library allows passing application context and metadata to the write-ahead logs (WAL) automatically. We then stitch the change data together and store it in a structured format in a destination cloud PostgreSQL.
We plan to charge for storage and compute if you’re a company storing >1M changes a month. We’re still early and it’d be amazing to get HN’s feedback.
What do you think HN?