RavenDB

And download here to get started: ravendb.net/download

Save an invoice. Crash before the event hits the queue. Payment went through. Nothing gets shipped. The order disappears. RavenDB's Queue ETL fixes this with zero application code. Full walkthrough: ravendb.net/articles/using… #distributedsystems #microservices

Listen to how #RavenDB helped #TheHarrierGroup, the UK's leading digital printer, focus on architecture that moves the needle. Download free 👉 ravendb.net/download #testimonial #nosql

We’ve redesigned the RavenDB Setup Wizard to focus on the dev experience: ✅ Integrated license generation ✅ Smart progress tracking ✅ Real-time error validation Read the #UX journey: bit.ly/4r5ktms

@McClellandRuss @TTrimoreau You have to see what's new in 7.2 💯

@TTrimoreau @RavenDB and @SQLServer. Works every time…

Which database are you using for your product? -Supabase -Postgres -Firebase -MongoDB I personally use Supabase for my project

@SumitM_X The plan isn’t “break isolation” or “ship nothing.” It’s admitting that dashboards are read problems and treating them as such. Write paths stay isolated. Read paths evolve. That’s usually the missing piece.

Each microservice owns its database. Now the business asks for a real-time dashboard requiring joins across multiple services. Your non technical manager asks you to do it in 1 sprint without breaking service isolation? What's your plan ?

@kristijan_kralj The unspoken part: shiny infrastructure doesn’t save weak foundations. It just lets you fail faster and at a larger scale. Boring, well-understood systems are what actually make teams productive.

The most powerful lesson I learned from working on 5 enterprise .NET projects: Solid engineering foundations over shiny infrastructure. Every successful .NET system I've seen shared the same patterns: * Tests that teams trust and run every day * Strong security awareness during development * Refactoring and improving the code continuously * CI pipelines that fail fast and stop broken code early * Clear boundaries between business logic and infrastructure * Architecture decisions written down so everyone understands why things look the way they do Weak foundations turn every change into a risk. Strong foundations make scaling boring. And boring and predictable is exactly what you want in production.

Still riding the @TechEx_Event energy where we met amazing fans and announced our newest release! 🚀 Hear CMO Ariel Sternfine on RavenDB 7.2. Thanks to everyone who took part and until we meet again, be sure to check out what’s new in 7.2: ravendb.net/why-ravendb/wh…

RavenDB is proud to be recognized by @FastCompany for our First Principles approach. Our CEO, @ayende, explains why fixing messy data and native security are essential for #AI to succeed. Read now: fastcompany.com/91485272/looki… #RavenDB #AInews

@univ_sc79925 That awkward moment when your query returns a '404: Meaning of Life Not Found.

Curiosity is a misplaced document in my database Anyone else having existential crises with their NoSQL queries?

@nonlinear_james @JetBrainsRider As for the 'flakiness,' we take that seriously. We've worked closely with the community to ensure that when you move from the IDE into production, the engine is rock solid. If the tools are getting in your way, we'd love to help you clear that cache and get back to building.

But is it more stable? I'm sitting looking at a solution with errors everywhere because Rider just spontaneously stopped being able to identify Linq/DynamicLinq/RavenDb Linq extension methods for the 50th time this month. And that's just the start of the flakiness which @nickchapsas has mentioned.

Rider 2026.1 EAP 4 Is Out! Rider now supports working with single-file C# programs, allowing you to create quick scripts, prototypes, and one-off tools written as a single C# file. For more information check out the release notes on our website 👉 jetbrains.com/rider/nextvers…

@nonlinear_james @JetBrainsRider It sounds like you're fighting IDE indexing, not the database engine. When Rider or VS lose track of Linq extensions, it’s usually a local tooling/cache conflict—frustrating for sure, but a different beast than database stability. @nonlinear_james

@purplepangolin @John_Stepek @ariaclast Definitely a good one! Thanks for the share, @purplepangolin

@John_Stepek @ariaclast This is a good post that takes a similar view ravendb.net/articles/the-r…

Have to say this accords with my gut feeling about AI, though I fully acknowledge that it's little comfort for those working in the areas most disrupted by this new "tool". (Note, Affleck uses some sweary words - typical Hollywood type! - so maybe wait until after the watershed)

@genxi_io Thanks for the shout-out. We're glad to be the foundation for your next big thing! @genxi_io

Discover how RavenDB blends performance, flexibility, and security to simplify database management for developers and businesses alike, redefining what a modern database can deliver. genxi.io/blogs/ravendb-…

@genxi_io That’s exactly the goal: making the 'redefinition' feel like standard operating procedure. Modern databases shouldn't force a choice between speed and safety. By moving the complexity into the engine, we ensure the developer's only job is to build, not to babysit.

@Mr_Pratap_Singh When the database handles its own indexing and security boundaries, you're finally free to focus on the actual product. Strategy shouldn't have to wait for a DBA. Happy building! 🐦‍⬛😉

Ever felt stuck building a system because your database just wouldn't keep up? I did — spent days tuning and tweaking just to get decent speed without losing flexibility or security. Then I tried RavenDB. Built a whole feature in 10 minutes that used to take DAYS. No crazy manual tuning, no compromises on safety. It’s crazy how this makes all those “fast but rigid” or “secure but slow” databases look totally obsolete. Why are we still settling for systems that block strategy instead of enabling it? #DatabaseStrategy #RavenDB #TechThatWorks

@Mr_Pratap_Singh That '10-minute feature' isn't luck—it's what happens when you stop fighting your infrastructure. Most databases force you to choose between performance and safety. We chose to move the complexity into the engine so it doesn't end up on your plate.

@Pavan_Kumar_Pal We also trade 'immediate consistency' for 'instant reads' by shifting the work to background indexing. We built a guardrail, not a sandbox. It’s a trade-off that favors performance over emergency calls. Nice to meet you! 🐦‍⬛😉

While RavenDB's approach sounds promising, it's essential to consider how these three elements can sometimes conflict in real-world application. What are the trade-offs in specific scenarios?

What if your database didn’t force you to choose between speed, flexibility, and security? Most settle for two at best. RavenDB breaks the rules—delivering all three without compromises. Missing this means settling for less in your entire strategy.

@Pavan_Kumar_Pal "In systems design, there’s no free lunch, only a choice of which problems you want to have. RavenDB trades 'ad-hoc spontaneity' for production stability. We won't let you run an un-indexed table scan that crashes your server at 3 AM.

@rogan_isabel 100%

Lowering the barriers databases place in the way of strategy, with RavenDB dlvr.it/TQbPzS