News for hackers. Stuff that matters.

A comment on Bridged Indexes in OrioleDB: architecture, internals and everyday use?. Parent comment

Re:Bridged Indexes in OrioleDB: architecture, internals and ... by iamdanieljohns on Friday May 30, 2025 @01:40PM (#44138386)
Is the need for Oriole negated by using a system that separates storage from compute like Neon, Xata?
[ Parent | on HN ]
Re:Bridged Indexes in OrioleDB: architecture, internals and ... by tudorg on Friday May 30, 2025 @02:56PM (#44138972)
Answering on behalf of Xata, it is orthogonal. I'm curious to try out Oriole on our platform when I get some time.
[ Parent | on HN ]
Re:Bridged Indexes in OrioleDB: architecture, internals and ... by nikita on Friday May 30, 2025 @02:31PM (#44138807)
(Neon CEO)

Not really. OrioleDB solve the vacuum problem with the introduction of the undo log. Neon gives you scale out storage which is in a way orthogonal to OrielDB. With some work you can run OrioleDB AND neon storage and get benefits of both.

[ Parent | on HN ]
Re:Bridged Indexes in OrioleDB: architecture, internals and ... by akorotkov on Friday May 30, 2025 @05:10PM (#44139924)
> OrioleDB solve the vacuum problem with the introduction of the undo log.

Way more than just this!

> With some work you can run OrioleDB AND neon storage and get benefits of both.

This would require significant design work, given that significant OrioleDB benefits are derived from row-level WAL.

[ Parent | on HN ]