How and Why Swiftype Moved from EC2 to Real Hardware

Re:How and Why Swiftype Moved from EC2 to Real Hardware by adrianpike on Monday March 16, 2015 @01:32PM (#9212886)

I've seen and fought issues with hanging and/or stalling EC2 instances, and the decision was made to move to physical hardware - it was one of those tradeoff choices you have to make about paying N dollars to throw money at hardware vs. M dollars at person-hours to investigate.

It's definitely kicking the can down the road (eventually you have to build such that failing infrastructure is transparent to your eng team), but I still think it was the right decision at the time. YMMV obviously. :)

[ Parent | on HN ]

Re:How and Why Swiftype Moved from EC2 to Real Hardware by makeitsuckless on Monday March 16, 2015 @03:56PM (#9213944)

I've had the odd problem with hanging/stalling instances before I learned to design for the cloud. Now those instances automatically get replaced with new ones and nobody would even notice if I didn't pipe the notice through to Slack.

Of course, this only works if whatever you use it for allows for this.

However, in most cases not using EC2 as a stateless throwaway computing resources is simply a matter of bad infrastructure design.

[ Parent | on HN ]