I’ve always wondered why OLTP databases didn’t go the route of tiered storage systems: save to memory, cache to NVME, save permanently to object storage, with different levels of guarantees for each level.
Congrats on this! Quite interesting for me as I have been working on vertical ERPs for a while, not at all related to manufacturing and as far as I know, accounting is usually the core of any ERP. Who is your ICP at companies in your target groups - ops managers? I’ve mostly seen CFOs being the drivers behind ERP purchasing.
This seems very good. Always wondering what are the usecases for this apart for observability/real-time analytics? Do people use this for incremental view maintenance in Postgres?
I understand Neon is open source and I think it’s an awesome product, but apart from the risks associated with longevity of open source once a company gets acquired - although the storage engine is open source, the control plane isn’t and is non-trivial to implement oneself. Orioldedb is positioned as a Postgres extension, which is must easier to setup (even on an existing operating database) than migrating to a completely different architecture that Neon provides.
Congrats with the launch! I think you’re tackling a core problem space - many people seem to go to v0 and just copy, paste from there. The drag and drop is really great. Curious - why did you go with Electron instead of Tauri? I imagine that would’ve significantly decreased your bundle size. Congrats again!
One thing none seem to notice is the rise of “Operational Warehouses” such as RisingWave or Materialize. A big ‘problem’ in OLAP, as the article mentions, is people expects aggregations or analytic views on live data. These solutions solve it.
In principle, this shows that just having incrementally maintained materialised views, really goes a long way towards achieving the HTAP dream on a single DB.
Does this mean the data source and destination both have to set up flight servers? I imagine then this won’t be useful for integration of third-party services.
I've been searching for a while for something as expressive as Rust but without a borrow checker and the powerful concurrency features of Go - then I found this!
Intelligence communities tend to pick very smart people who are particularly good at acquiring niche skills and operating under extreme situational uncertainty. I think those are valuable attributes for someone in business.
Good question! Feel this is just a vague way of referring to formal compliance requirements for software rather than technical functionality supporting large scale operations.
Looking at the effort being put in it seems there’s a massive market for proper Postgres analytics / columnstore, which is very telling of the pain involved in moving data between systems.