DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Join us today at 1 PM EST: "3-Step Approach to Comprehensive Runtime Application Security"
Save your seat
  1. DZone
  2. Data Engineering
  3. Databases
  4. What's Next for RavenDB

What's Next for RavenDB

Oren Eini user avatar by
Oren Eini
·
Jan. 10, 13 · Interview
Like (0)
Save
Tweet
Share
3.90K Views

Join the DZone community and get the full member experience.

Join For Free

image after 2.0, what comes next? ravendb 2.0 is a massive release, close to 5 thousand commits, 6+ months of work, a team of close to 70 people working on it.

it also thought me a very good lesson about cutoffs. i don’t like them. in particular, someone who wanted to run on the stable version was stuck with 6 months with no features, and only hot fixes as needed.

instead, i would like to go to a more streamlined model of a stable release every 6 – 8 weeks. that gives us a proper time frame for doing changes, but doesn’t leave people “in the cold” in regards to stale versions.

so that is what we are planning in terms of process . but what about the actual features ? surprisingly enough, we have enough more lined up for you.

  • robust sql replication (already implemented, and waiting for additional testing & goodies). to better support reporting.
  • indexing snapshots and unlimited result set server side processing.
  • multiple index batches and independent indexing. prevent a slow index from slowing down all indexing.
  • restructuring of temporary / auto indexes.
  • auto index merging. (even smarter behavior with regards to optimizing indexes, removing unused indexes, etc)
  • write index output to documents. allow to do things like multi stage reduces.
  • winrt & mono touch & mono for android client support.
  • more comprehensive client side caching.

and those are just the things we have as high level items smile .

Release (agency) Mono (software) Replication (computing) Cache (computing) teams Android (robot) Commit (data management) Document sql

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Top Authentication Trends to Watch Out for in 2023
  • A Beginner's Guide to Back-End Development
  • How to Secure Your CI/CD Pipeline
  • Handling Automatic ID Generation in PostgreSQL With Node.js and Sequelize

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: