Re:How ReadMe Went from SaaS to On-Premises in Less Than One...
by icebraining on Tuesday November 01, 2016 @04:38AM
(#12844181)
all the potential customers I asked said that they were comfortable managing their own Docker environment
Can we trade customers? Last year I've had to install our software in a CentOS 5.5 system. With no root access. Can't say compiling Python 2.7 and all that crap to run on a user account was much fun, but hey, at least they're billable hours.
Large, and especially public, companies seem to be the worst. SMBs were happy to receive a VM or OpenVZ image.
Re:How ReadMe Went from SaaS to On-Premises in Less Than One...
by user5994461 on Tuesday November 01, 2016 @06:59AM
(#12844641)
> single horizontally-scaled server
Quick edit: That's vertical scaling if you have a single server that you make bigger.
Re:How ReadMe Went from SaaS to On-Premises in Less Than One...
by piotrkaminski on Tuesday November 01, 2016 @07:13AM
(#12844684)
No, I actually meant "a single kind of server process that you just run more instances of to scale" but couldn't find a concise yet accurate way of expressing it. This differs from the setup described in the article since they have four different kinds of servers that need to be coordinated, interconnected, etc. -- a more complex setup that likely benefits from Replicated.
One difference is that I decided to stick with a raw Docker container rather than going with Replicated (who are really nice people, don't get me wrong). In my case, everything runs on a single horizontally-scaled server so it's pretty easy to get running "manually". Also, all the potential customers I asked said that they were comfortable managing their own Docker environment, and some would actually prefer to get Docker images since they'd be easier for them to manage than "virtual appliance" VMs.
Another difference was that I use Firebase for the app's datastore and Google doesn't (and likely never will) offer an on-premises version. This was a show-stopper for nearly all customers, but it turned out that offering at-rest encryption of sensitive data with a key that never leaves their premises was sufficient to get through many of the security reviews. This obviously won't be acceptable to everyone but it can be useful to know that even if you have a fundamental dependency on an external third-party service there may be a way to keep using it in your "on-premises" product.