March 18 Meetup update is going online: Building a Grown Up Database
Due to the Coronavirus issue that has been going around, my March 18 session has been moved to be online only.
You can register to the event here, we’ll also be sharing it live in the RavenDB facebook page.
As a reminder, the talk is: Building a Grown Up Database
A database is a complex, often fussy beast. For years, Oren Eini has made his living by fixing performance issues of various kinds. After seeing the same mistakes happen again and again, Oren decided to build his own database where these problems will never arise.
In this Webinar he will talk about the kind of features that make RavenDB a grown up database:
-- It doesn't need a full-time babysitter
-- Uses AI automatic indexing and self optimizing engines
-- Understands the operational environment and adjusts to it without the need for a human in the loop
-- High Availability
-- Secured development
Hello Oren. I disagree about the assumption that a lot of configuration options almost always means complex setup that only experts can do. In my opinion, 90% of the options are almost never touched and you (or your DBA) rely on the system to be able to figure out a sensible default for them depending on your environment (hardware, OS, etc.) However, if you do need to use them (e.g. you have a production issue and you need a quick fix now, investigation to be done later, you find out that some XYZ settings combo can fix your problem) - that can be done. On the other hand, if you don't expose that lot of config options and your database is extremely stable so you (as a database vendor) never hit aforementioned situation - I believe that is getting close to a managed database (e.g. you go to a cloud provider, pay them 500$ each month and they handle everything from their end, including hardware failure, backups, etc.)
A major issue here is how often do you need to touch those configuration values. And in many cases, you do need to do so. Looking around, check these out:
And the difference is when you need to do that.
Note that RavenDB also has such configuration, because sometimes you need to. But that is the rare case
Its true that popular relational databases suffer from puzzling set of default settings. I'm guessing it's a combination of number of scenarios they are used in as well as a legacy codebase that's hard to evolve