My goal is to use RavenDB for portal solutions that are hosted. When a new client wants to use my portal solution, it will be tedious to have to come into RavenHQ, create a new database, collect the new connection string information and API Key and then create the portal and configure the web.config with the connection string.
We currently do not provide a public API for provisioning databases. However, we plan to finalize a public API in the next few months (probably September time frame).
We currently do not provide a public API for provisioning databases. This feature was pushed back in favor of EU instance support and will be re-prioritized after we release official support for V2.0. If this feature is blocking you from being able to use RavenHQ, send a support ticket to support@ravenhq.com and we'll see what we can do to help.
I'm gonna +1 the request for this.
I too want to +1 this request. So far this is the major technical hurdle with regards to me creating a start-up company.
Hey guys, thanks for your interest in this feature. We'll be prioritizing this very soon. Could you please provide some of your use cases for this feature? How would you be using it in your system? Would you be using bundles? Replication? How many databases would you be creating? Would you have high turnover in database creation and termination?
Thanks for your feedback!
Jonathan Matheus
Jonathan,
We use RavenDB HQ to host the data for our portal solutions. The portal solutions host our clients customer data. Their customers would come log in and do things like update their address.
The CRM system is setup to auto sync with RavenHQ. The idea would be to add the ability to send in our parent API Key to retrieve a sub Account Key and Database for each of our clients.
Then we could add the provisioning of a client DB under our umbrella of databases. I am sure there is a way to structure one document database so that each client only sees their data.
That implementation is not ideal. It makes it all together more secure for them to be their own database.
Hi Jonathan,
My current plan would spin up a single raven DB database per customer. As for high turnover I want to limit it to be a monthly subscription based service and therefore could see the need to terminate databases after performing an export of all the content. The premise of this is that each customers data would be isolated. As my product will be crossing multiple market verticals this is essential to my solution as I cannot predict the customer base yet. At the same time the usage patterns and data size would depend upon how much each customer used the system.
There would also be another database used as the master database storing the customers high level info and system settings etc.
If all plans proceed as I hope, I think we will see less than 20 db's by the end of this year, and then growing next year up to 100 db's.. These numbers are just projections right now.
In some scenarios I could imagine the need for replication. I have to admit I haven't researched any of the other bundles yet.
Thanks
Pete
Any progress on being able to spin up a new DB in RavenHQ as described here http://ravendb.net/docs/server/multiple-databases ?
We are working on some different changes to our platform that will allow us to support the programmatic creation of new tenant databases. This may be through a public API, or through a special plan configuration that allows you to create additional database tenants from within the RavenDB Management Studio. We don't currently have a firm timeline on when these new features will be implemented.
Is this available in 2.5?
Having programmatic tenant databases would allow our business app to be transfer to using ravenhq. Any updates on when this might happen?
This would be a great feature. Would love to know if this is on the road map and when it might be delivered.
Any movement on this? It's been a long time since this feature was requested and we would very much like to make use of this.
It's been almost 7 years now. A PaaS company without an API? Mind boggling.