Hi HN, we’re the builders of Bemi. We enable automatic tracking of database state changes and surface this information in an easy-to-use platform. We turn complex and noisy data changes into clear, human-readable logs allowing ops and customer success teams to tackle inbound inquiries independently - saving many engineering hours!
We are still early though and would love your feedback. What do you think HN?
This is a great idea and seems like it could be super useful. We've built something sort of like this by firing off events to Amplitude from the server side to cover state transitions by users, including the old state as a property for later inspection. But doing it automatically from the DB txlog makes a ton more sense.
Thanks throwaway-blaze! And that's actually very interesting to hear that you've already covered something like this using Amplitude events. Do you remember what your initial motivation for doing this was? Were you trying to capture server-side state transitions for analytics or for troubleshooting purposes?
Thank you for the interest! We're too early stage to start hiring right now. Let's stay in touch for now, can you DM me?
For anyone else that's interested in getting involved - we have some open-source libraries that we'll work to make more accessible for contributions down the line. Stay tuned for updates, and appreciate the interest!
Yup so you got it exactly right that Bemi is higher level than Debezium. We actually do use Debezium under the hood, but we also enhance this lower-level data with context via lightweight application libraries. So we're integrating at both the database and application layers on the write side.
We are still early though and would love your feedback. What do you think HN?