FUTURE POSTS

1. RavenDB: .NET Aspire integration - one day from now
2. RavenDB on AWS Marketplace - 3 days from now
3. Production postmortem: The race condition in the interlock - 6 days from now
4. When racing the Heisenbug, code quality goes out the Windows - 8 days from now
5. Pricing transparency in RavenDB Cloud - 10 days from now

There are posts all the way to Apr 11, 2025

RECENT SERIES

1. Production Postmortem (52):
   12 Dec 2023 - The Spawn of Denial of Service
2. RavenDB (13):
   25 Feb 2022 - Domain Modeling and Data Persistency
3. RavenDB 7.1 (6):
   18 Mar 2025 - One IO Ring to rule them all
4. RavenDB 7.0 Released (4):
   07 Mar 2025 - Moving to NLog
5. Challenge (77):
   03 Feb 2025 - Giving file system developer ulcer

RECENT COMMENTS

• Nice… I live April 😉
  By Pierre on Introducing Rook AI
• John, We aren't writing microcode, we are (usually) writing C#, then ensuring the generated assembly is accepted. However...
  By Oren Eini on Optimizing by 170,000%(!) by not being silly
• > (yes, we design some pieces of RavenDB with CPU microcode for performance). Can you elaborate on this? I have never hear...
  By John on Optimizing by 170,000%(!) by not being silly
• Soren, Probably... That piece of code was written (and never looked at) in 2017, IIRC It wasn't a real issue (since it ...
  By Oren Eini on Optimizing by 170,000%(!) by not being silly
• Wouldn’t some of the roslyn code analyzers suggest that this should be a static? I’m curious:)
  By Søren Trudsø Mahon on Optimizing by 170,000%(!) by not being silly

Syndication

Main feed
Comments feed