Doing it again, twenty years later: introducing Quill

I started RavenDB in a spare bedroom, because of a problem that wouldn't let me sleep. Everywhere I looked, applications were fighting their own database. ORMs papering over a model that didn't fit. Indexes missing or just bolted on after production failures, without attention or concern to how to do this properly.That was the common situation in the industry; accepted because databases required a lot of expertise and no one had time to do the right thing with the next release date looming. The industry's answer was always another layer of tooling on top of a design that was already wrong. So I built a database where those things were expected, that would behave properly even if it didn’t have a full time babysitter to make sure it survived production.Twenty years later, I'm looking at the same shape of problem again.The same feeling, a second timeIn the past couple of years, we built RavenDB's AI capabilities and we've spent the last year helping our customers launch complex AI…