Oren Eini
CODE Author
Oren Eini has over 15 years of experience in the development world with a strong focus on the Microsoft and .NET ecosystem. And he has been a Microsoft MVP since 2007. Oren’s main focus is on architecture and best practices that promote quality software and zero-friction development.
An internationally known presenter, Oren has spoken at conferences such as DevTeach, JAOO, QCon, Oredev, NDC, Yow! and Progressive.NET.
Oren is the author of the book DSLs in Boo: Domain Specific Languages in .NET, published by Manning (http://manning.com/rahien/).
Oren Eini is the founder of Hibernating Rhinos LTD, a Israeli-based company, which produces RavenDB, NHibernate Profiler and Entity Framework Profiler.
Articles Authored
-
C# for High-Performance Systems
Last updated: Friday, December 26, 2025
Published in: CODE Magazine: 2024 - March/April
Oren Eini, creator of RavenDB, discusses and demonstrates how to use C# for building high-performance systems. Oren proves through examples that a high-level language like C# is suitable for low-level system programming. His examples compare the performance and memory consumption of different methods, including LINQ, a StreamReader + Dictionary approach, and the use of System.IO.Pipelines.
-
What’s New in RavenDB 2.5
Last updated: Friday, December 26, 2025
Published in: CODE Magazine: 2013 - September/October
In this article Oren Eini highlights what he views as the standout additions in RavenDB 2.5—result transformers, scripted patching, SQL replication, unbounded streams, dynamic reporting, concurrent writes, and indexing optimizations—explaining how they enable richer server-side projections, safe large exports, easy migrations and RDBMS integration, faster writes and smarter indexing; overall he argues these features make RavenDB a more powerful, production-ready, “zero friction” document database worth adopting.
-
Getting Started with RavenDB
Last updated: Friday, December 26, 2025
Published in: CODE Magazine: 2012 - March/April
You might have heard some things about NoSQL; how Google and Facebook are using non-relational databases to handle their load. And in most cases, this is where it stopped. NoSQL came about because scaling relational databases is somewhere between extremely hard to impossible.