2 ms·

Thanks. Please see my response to thinkbohemian's comments. My point is that using a PAAS illustrates some sacrifices a customer has to make if they've traditi

by DASD 14y ago

Thanks. Please see my response to thinkbohemian's comments. My point is that using a PAAS illustrates some sacrifices a customer has to make if they've traditionally been accustomed to hosting their own infrastructure. Some customers are simply not aware of expectations they might need to change. Nothing more or less than that. I'm not sure bob@heroku.com helps me here unless I was previously introduced to Bob from a notification of a general support e-mail. Again, I'm speaking without paid Heroku experience here but to me it seems the equivalent of a "Hiya guys!" greeting. Heroku is owned by Salesforce which describes itself as an "enterprise cloud computing company."

nthj 14y ago
sure, that tracks. I think our main difference is over whether or not the stacks are fundamentally the same. The legacy apps can still run the same Rails version, can still run the same Ruby version, and can still deploy using `git push,` it's just a more powerful abstraction. To me, this migration feels like the equivalent of "Oh hey, you've gotta upgrade your database version and download a few security patches for your OS", which any enterprise-level company is going to be more than familiar with. It's not like they came out and said "well bugger, we don't support Rails 2 anymore, you gotta rewrite all your app code to work in Rails 3." I would understand any frustration then. shrugs