5 ms·
Yeah, one of my clients ran on OSS Parse for a while too but at the time of Parse.com shutting down OSS parse was not stable at all. In the end we decided to r
by vbsteven 8y ago
Yeah, one of my clients ran on OSS Parse for a while too but at the time of Parse.com shutting down OSS parse was not stable at all.
In the end we decided to rewrite the whole thing as a Java/Spring/Postgres monolith on Kubernetes. The rewrite took 3 months from decision to production and has been running fine for two years now. Initially on AWS and more recently the staging/dev environments have been moved to DigitalOcean in a couple of hours.
After the pending acquisition we’ll probably move the whole thing to Azure and I expect that to take a couple of days.
- lucasverra 8y agoquick question : if you are happy on DO, why switch to Azure ?
- vbsteven 8y agoWe switched our staging/dev environments to DO because of cost. A small Kubernetes cluster and hosted Postgres does not cost much there and is very easy to setup. But their hosted Kubernetes and Postgres services are still in “early access” so I’m holding off running production services on there for now. The switch to Azure will likely happen post-acquisition to move everything into the infrastructure of the buyer.