4 ms·
I took one look at "baasil.io" and saw the typical landing page with a "Plans" link at the top and questioned why anyone would want to take a dependency on this
by nbevans 10y ago
I took one look at "baasil.io" and saw the typical landing page with a "Plans" link at the top and questioned why anyone would want to take a dependency on this. If there is some OSS project behind the plan-based charade then that's fine.
"Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't have to change any of your application code or change infrastructure providers."
But so you can with AWS and Azure - especially with their Docker offerings. So I'm not sure what problem baasil.io actually solves? If anything it just adds to the list of dependencies and points of failure.
- jondubois 10y agoThe main benefit of Baasil.io is that it offers developers a boilerplate/framework which they can extend with their own code (to build scalable realtime apps and services) - Any app/service built on top of this boilerplate can be automatically scaled to 1000 hosts/nodes using a single command. Users don't have to use Baasil.io, but if they do, they will get the best possible support - For example, a customer can give us access to their Rancher control panel and this would allow us to SSH into their machines to help resolve any problems in a hands-on way. It's probably more accurate to describe it as "DevOps as a service - With a focus on realtime apps/services". The value proposition is probably closest to Cloud 66 http://www.cloud66.com/ http://www.cloud66.com/ except more focused on realtime apps. Another similar service is Zeit.co https://zeit.co/ https://zeit.co/ - Except Zeit.co only runs Node.js. Baasil.io can be extended with components written in any language.