How and Why Swiftype Moved from EC2 to Real Hardware

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

My 5cent:

If you have lots and lots of money and a high margin business, do yourself a favor and go with Amazon (much less hassle with contract management and low level challenges).

If you need to scale month to month and are growing 50% per month, go with Amazon.

If you are very small and can live with 10 instances, go with Amazon.

If CAPEX doesn't help you and for whatever reasons you need to spend OPEX, go with Amazon.

If you need many (types of) machines for failover but which otherwise mostly idle, go with Amazon.

Otherwise it's always cheaper to buy or rent hardware. Amazon is very expensive (TCO).

If you base your decision on hype, you're screwed.

* Amazon stands for Cloud Provider, personally I'm choosing Digital Ocean with Mesos/Docker.

* Except S3 which is a no brainer to use.

[ Parent | on HN ]

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

> If you need to scale month to month and are growing 50% per month,

Then rent more servers.

> If you are very small and can live with 10 instances,

Then rent a few servers.

I maintain that there are extremely few cases for a typical website to use the cloud. To handle peaks, it is both simpler and cheaper to keep enough capacity just idling around than spinning up and down Amazon instances. The cloud is almost always a useless hype. It can be different if you can architect to use the various services Amazon provides.

[ Parent | on HN ]

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

From my experience renting more servers with 50% growth is a challenge. A lot of things go wrong when installing a lot of servers each month.

Also from my experience, with 10 instances the money you save with custom servers is negligible and contract and SLA management, multi datacenter etc. is easier with a cloud provider than renting servers. At least where I've rented servers in the past.

[ Parent | on HN ]

Re:How and Why Swiftype Moved from EC2 to Real Hardware by Negitivefrags on Monday March 16, 2015 @04:36PM (#9214211)

I'm not sure where you see a difference between a VM and physical hardware when it comes to provisioning.

Sure, the physical hardware takes 1 hour rather than 1 minute to spin up, but the process is otherwise entirely identical.

[ Parent | on HN ]

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

1 hour? Welcome to 2015! OVH spins your server up in two minutes.

[ Parent | on HN ]

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

Why rent more servers when it's so much easier to spin them up as you need them in AWS and tear them down (and no longer pay for them) when you don't. If you're expecting unknown change in scale, it's so much easier to be able to just spin up servers to keep up than anything else.

> To handle peaks, it is both simpler and cheaper to keep enough capacity just idling around than spinning up and down Amazon instances.

At a growing website, you have no idea how much "enough" is. Why try to estimate caps when you don't have to?

[ Parent | on HN ]

Re:How and Why Swiftype Moved from EC2 to Real Hardware by kovyrin on Monday March 16, 2015 @02:26PM (#9213281)

Absolutely, 100% agree. Thanks for the comment!

[ Parent | on HN ]