What if I buy two Embedded licenses - can I then use two processes? :) Why does the Embedded version even have UseEmbeddedHttpServer if nothing can use it?
For the sake of keeping my product install ultra simple I'd really like to stick to embedded at first. It looks like I am now faced with hosting ASP.NET within my Windows Service, or modifying my installer to auto-install RavenDB Server, just because of a licensing gap...
Also, any idea what the ballpark price for RavenDB Server will be? $1,599, $15,999?
I love RavenDB and I'd love to find a way to make this work without compromising my end user experience.
On Monday, 23 April 2012 18:05:37 UTC+1, Oren Eini wrote:
No, embedded means using only within a single process. Not when you have multiple processes.
There is going to a RavenDB ISV Server version, which will give you the ability to just deploy standard ravendb at the customer site, royalty free.
I'm migrating my product (octopusdeploy.com) to RavenDB and I'm just about to buy a license. My application is split into two pieces - a Windows Service and an ASP.NET frontend. Both processes run on the same machine. The only reason they are separate is that I need some scheduled tasks to run in the background, and hosting ASP.NET in a Windows Service isn't fun.
I don't want to force customers to have to buy a server license, so I'm using the OEM version. Since I have two processes touching the same database, the way I've implemented it is to use the embedded server in the Windows Service, and then to set UseEmbeddedHttpServer and have the ASP.NET frontend connect to the embedded instance over HTTP using the client API.
I'm still only using the capabilities of the embedded server, so I assumed this was "fair" and within the terms of the OEM license. But reading about the possibility of an OEM/Server version has me second guessing that now.
Is it within the terms of the OEM/Embedded license to use UseEmbeddedHttpServer and have a second process connect to the embedded instance? And will it still be OK under the new license model?
I'm all for a re-distributable OEM/Server version so that I can get RavenDB out of my process, I'd just like some clarity.
On Tuesday, 28 February 2012 23:04:49 UTC, Oren Eini wrote: