Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 5,971 | Comments: 44,508

filter by tags archive

RavenDB Conf VideosTailored database solutions with Voron


In this talk, I’m creating, live on stage, a database for handling time series data with the goal of handling 100 billion events per year.

And it actually worked!

More posts in "RavenDB Conf Videos" series:

  1. (13 May 2014) The tale of RavenHQ - An Ops Story
  2. (12 May 2014) Lap around the new HTML5 Raven Studio
  3. (09 May 2014) Scalability and High Availability with RavenDB
  4. (08 May 2014) RavenDB 3.0
  5. (07 May 2014) Extending RavenDB with Bundles, Plugins, and Listeners
  6. (06 May 2014) Mastering Date and Time Data in RavenDB
  7. (05 May 2014) Abstracting RavenDB
  8. (02 May 2014) Document Based Messaging with RavenDB 3.0
  9. (01 May 2014) RavenDB, CQRS and EventSourcing
  10. (30 Apr 2014) Modeling Tricks my Relational Database Never Taught Me
  11. (29 Apr 2014) Tailored database solutions with Voron
  12. (28 Apr 2014) Panel Discussion - The good & ugly of working with RavenDB
  13. (25 Apr 2014) Diving into Voron
  14. (24 Apr 2014) Introduction to document database modeling with RavenDB

Comments

Dan Liebster

This is a really interesting presentation. You stated in the presentation that Voron itself will not be a product. I understand that you are going to use it as the underlying datastore for RavenDB, but will the Voron trees be completely abstracted away, or will you be augmenting the RavenDB API's so that there will be the possibility of using trees more directly (as you do in this presentation for time-series data)?

Ayende Rahien

Dan, Voron really is too low level for most business apps needs. And there is a LOT more to building data stores than just knowing the API. There are a lot of additional concerns. We intend to use Voron as the building block for customized data solutions.

That doesn't mean we won't be licensing this out if people really want this, but it would likely be a very different model than RavenDB.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. Paying the rent online - about one day from now

There are posts all the way to Aug 03, 2015

RECENT SERIES

  1. Production postmortem (5):
    29 Jul 2015 - The evil licensing code
  2. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
  3. API Design (7):
    20 Jul 2015 - We’ll let the users sort it out
  4. What is new in RavenDB 3.5 (3):
    15 Jul 2015 - Exploring data in the dark
  5. The RavenDB Comic Strip (3):
    28 May 2015 - Part III – High availability & sleeping soundly
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats