How and Why Swiftype Moved from EC2 to Real Hardware

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

I'm convinced hybrid cloud is the way to go. Anything needing high IO performance should be on dedicated. Anything needed CPU/memory elasticity (worker nodes, etc) should be in the cloud. Assuming you can get low latency connectivity into AWS with DirectConnect, this might work?

[ Parent | on HN ]

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

The speed of light is not your friend. You can never compete with the latency of a local network versus even the fastest connection to a cloud provider.

[ Parent | on HN ]

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

Yeah, that (worker nodes, async processing, etc) seems like one of those ideal use-case for clouds that I could definitely support as a viable option for companies that aren't ready for all-in cloud deployment.

[ Parent | on HN ]

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

Cpu also generally sucks due to cache thrashing on non-trivial datasets

[ Parent | on HN ]

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

Heh. So what is a good use case for EC2?

[ Parent | on HN ]

Re:How and Why Swiftype Moved from EC2 to Real Hardware by fleitz on Tuesday March 17, 2015 @01:54AM (#9216489)

When you have highly variable load.

eg. Netflix probably spins up thousands of servers for a few hours.

[ Parent | on HN ]