3 ms·
Shame it’s not OSS but I get that. The ‘no lock-in’ statement on the site; if we would see speedups in both dev and execution performance by using this and deve
by tluyben2 5y ago
Shame it’s not OSS but I get that. The ‘no lock-in’ statement on the site; if we would see speedups in both dev and execution performance by using this and develop everything on it from that point to improve working with data easier across the enterprise, how are we not locked in when we you decide to do something else or sell to Oracle? The latter happened to us, quite exactly and that’s why no OSS is no go for dev infrastructure.
Definitely nice work though and best of luck!
- wuputah 5y agoHi, JD here, Hydra's CTO. It's still early days and we are considering open source; for now, we wanted to leave our options open, and OSS feels like a one-way door. I think you make a great point here - thanks for sharing your past pain / experience. Definitely food for thought. Our "no lock-in" claim refers to your data, since Hydra is Postgres, you're not stuck using "HydraDB" forever -- it's relatively easy to migrate in or out since you can use well established Postgres tools. We also are open to licensing the product should you wish to self-host, on-prem, etc.