3 ms·
We're not a Cloud Foundry company, we really don't care about PaaS that much. We just needed something that fit our unique use case and that, in case the PaaS v
by sgrove 14y ago
We're not a Cloud Foundry company, we really don't care about PaaS that much. We just needed something that fit our unique use case and that, in case the PaaS vendor didn't feel the same sense of urgency that we did for something we need, we could add in ourselves - I'm sure you're very familiar with that, Solomon. We're happily sending changes upstream whenever they're sufficiently high quality for everyone else.
So, 1.) We didn't want to (poorly) re-invent it ourselves, and 2.) We didn't find any existing provider that was able to match our schedule and needs. Cloud Foundry let us side-step both of those problems and launch. We'd be dead by now if we had waited.
- shykes 14y agoHi shrove, thanks for the precision. You have a point - you're tackling a particular edge case in deployment which most paas providers are neglecting, leaving you vulnerable to shifting priorities in their roadmap. It makes sense for you to take your destiny into your own hands, so to speak. My question was triggered by your article but not particularly targeted at you - I was hoping to start a philosophical conversation on the pros and cons of running a business on top of IP which you don't own. So far I don't see any takers ;)
- sgrove 14y agoSgrove. Sean Grove. And when you have a chance, I'd certainly be happy to take you out for drinks and chat for a bit. Sometime next week, perhaps?