+972 52-548-6969
What is new in RavenDB 3.5Smuggling data across servers
This feature is meant primarily for users that work with multiple instances of RavenDB. The common scenario is production/staging/development and needing to move data around between them. Previously, you would have to manually move data using import or export, or set a bunch of scripts to run the smuggler with the right commands.
In RavenDB 3.5, we have turned that into a full fledged feature.
The nice thing about this, you can just set it up as you want, with the right databases and configuration that you need to send. By default we use incremental option, so you can run this over time and only get the new stuff.
The idea is that you can use this to move the data from one environment to the next. You can also click on the Show JSON button and get the data you need to script this (across all dbs) in an automated (and possibly scheduled) manner.
More posts in "What is new in RavenDB 3.5" series:
- (12 Aug 2015) Monitoring support
- (11 Aug 2015) Monitoring active I/O operations
- (10 Aug 2015) Filters & transformers with RavenDB Replication
- (06 Aug 2015) Collection Specific Replication
- (15 Jul 2015) Exploring data in the dark
- (14 Jul 2015) My thread pool is smarter
- (10 Jul 2015) Smuggling data across servers
Comments
The one big thing this is missing is text telling you whether you're smuggling data from the target server or to the target server. It's in the docs, I'm sure, but if I'm responding to a page at 3am I want an extra notification, just to be sure.
dhansnan, Hm, you are correct. We should change that to destination server url.
Comment preview