3 ms·
Just got the same shocking message, I had the same feelings about orchestrate, I worked with orchestrate for a wile but I was skeptical as you (glad for that) s
by mamod 10y ago
Just got the same shocking message, I had the same feelings about orchestrate, I worked with orchestrate for a wile but I was skeptical as you (glad for that) so I switched to self hosted solution few months ago to a new data base "crate.io" it wasn't that hard to migrate code base, no data transfer though since I stopped using it before launching my project :)
again I'm glad I followed my hunch :)
- cyberferret 10y agoYes, I am kind of wishing I had followed my gut feel too. I had tried AWS's NoSQL system, but had interminable trouble getting it to integrate with BotKit - Then while researching things I saw that Orchestrate had a plugin which integrated easily, and we managed to get it working in an afternoon and were delighted. Now it means we have to pull out all that code and integrate another NoSQL system in there for data storage. I am glad that we held off from launching our bot to the public this month - we were waiting until the new year. So fortunately I don't risk losing any real customer data - only beta tester data. Inconvenient, but not insurmountable. It has made me a lot more reticent to consider other small players in our stack though - might stick with AWS all the way from now on.