6 ms·

Before Heroku, "just works... for a long, long time" meant "for a few weeks until the database goes down, or the firewall needs to be patched, or, something," a

by nthj 14y ago

Before Heroku, "just works... for a long, long time" meant "for a few weeks until the database goes down, or the firewall needs to be patched, or, something," and you have to bring in a $150/hour consultant to figure out what went wrong. If you paid Heroku an enterprise-level $10k/month for "just works, for a long, long time", I'm sure they'd gladly dispatch a Rails' consultant to handle the migration for you, and you'd never hear about it. $50/month does not buy you "works for next 3 decades" technology. A business owner would gladly take "3 hours of stack migration every few years" over requiring a high-dollar consultant every few weeks, especially since the consultant probably comes with a retainer he has to pay whether he has problems or not. [also, I'm sure the personal account was a bob@heroku.com address, vs a support@heroku.com address.]

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

by nthj 14y ago

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