5 ms·

I am sure plenty of people go to Heroku from AWS and vice-versa of course. But don't underestimate the amount of work it is to switch either, you already have

I am sure plenty of people go to Heroku from AWS and vice-versa of course. But don't underestimate the amount of work it is to switch either, you already have a working, running solution today. You maybe better off taking a week or so of time and just automating your AWS infrastructure using either OpsWorks or Ansible etc. Then deploy something like the ELK stack for the monitoring and logging to make that easier and be done with it. I am not saying any of this is trivial, but once you do it you will not have changes every day. My bet is it would take you a week or more to move, and it would probably take a week or so to automate most of your "issues" today. But at least with AWS today you know how your app is performing and acting etc. If I was in your position, I'd probably try to automate the pain points first, then move as a last resort. Unless there are other reasons for wanting to move. But either way, just don't underestimate the work to move.

noahc 12y ago
+1. We weren't on AWS, but we had co-located rack space and we moved our main rails app that has been in development for 4 years over to Heroku. It took much much much longer than anyone expected. Like we thought it was a 4 man weeks of work, turned out it was a few man months of work. Most of the work we had to do centered around data. The rails app it self pretty much worked. We had to change a few things moving from mySQL to Postgres. We depended on a gem that apparently was only tested against mySQL and when we moved to Postgres had to scramble pretty hard to get stuff fixed. How am I going to get this legacy Domino/Lotus Notes system and AS400 to talk to this postgres database or am I going to build APIs around it, etc were harder to solve. We moved to Heroku because we didn't have the time or skills to do devops well. Heroku has dramatically reduced the amount of time we spend around devops to the point that most months it approaches 0. We also have been using New Relic, which I don't think we would have installed without Heroku. This tool is amazing and has allowed us to respond to trends much better. Our move to a more SOA infrastructure drove us to Heroku, and for us it was totally worth the switch. If you, or anyone, has specific questions feel free to reach out: noah@noahc.net

noahc 12y ago

+1. We weren't on AWS, but we had co-located rack space and we moved our main rails app that has been in development for 4 years over to Heroku. It took much much much longer than anyone expected. Like we thought it was a 4 man weeks of work, turned out it was a few man months of work. Most of the work we had to do centered around data. The rails app it self pretty much worked. We had to change a few things moving from mySQL to Postgres. We depended on a gem that apparently was only tested against mySQL and when we moved to Postgres had to scramble pretty hard to get stuff fixed. How am I going to get this legacy Domino/Lotus Notes system and AS400 to talk to this postgres database or am I going to build APIs around it, etc were harder to solve. We moved to Heroku because we didn't have the time or skills to do devops well. Heroku has dramatically reduced the amount of time we spend around devops to the point that most months it approaches 0. We also have been using New Relic, which I don't think we would have installed without Heroku. This tool is amazing and has allowed us to respond to trends much better. Our move to a more SOA infrastructure drove us to Heroku, and for us it was totally worth the switch. If you, or anyone, has specific questions feel free to reach out: noah@noahc.net