+972 52-548-6969
Empowering your queries with RavenDB
time to read 1 min | 32 words
I wrote an article on DZone that explores some of the new possibilities that RavenDB 5.1 enables.
You can read it here, and as usual, I would love to hear your feedback.
Comments
Though I read all your posts here and keep up with RavenDB news, I must say the article shed new light on the possibilities RavenDB has.
You used the term "prediction" several times, but the examples were not predictive, which is a bit confusing.
The only typo worth mentioning is "level" instead of "lever", which puzzled me for a minute.
Peter,
Thanks, I submitted an update to the article to fix the typo. I'm using prediction here because I'm using: PredictionEngine for the ML piece, do you have a better term for that?
The prediction engine part of the ML library I would assume is geared towards producing extrapolated (eg future) values, hence the name. You did mention the possibility of predicting the next value of a time series in passing, but your examples were all querying existing data. It would have been nice to see an example of expected values, or even better, expected product demand.
BTW the DZONE search is poor, and the facet selection function didn't work as far as I could see.
Interesting comment there, someone is working on a bot to post comments with canned variations. Buggy though, the whole template was posted.
Peter,
The idea is that we are querying the prediction of the engine. Or the analysis of the engine, to be rather more eact.
Predicting future values is a relatively simple matter of feeding the input to the model, which is something that you can do using this pipeline.
And yes, I'm seeing a HUGE spike in the spam in the blog.
Comment preview