Live data from Hacker News

Hyper.sh – Effortless Docker Hosting

hyper.sh

51–60 of 218 posts

Re: Hyper.sh – Effortless Docker Hosting

#51
post #34

Earlier quoted context omitted.

Edit: I went ahead and signed up for an account and made a container. The floating IP for the container appears to be an LA IP address. Their host appears to be ZenLayer, a Chinese hosting company that can apparently do co-location in LA, so while the IPs geolocate to China, it's possible they are indeed hosting in LA. The CPU is a E5-2630 v4. Original: I'm pretty sure they're entirely hosted on AWS. Given that they…

I have a feeling a huge chunk of the projects we see here are run on AWS. Duckduckgo runs on AWS. For getting things started quickly at a low initial cost, it's usually more viable to use a hosted solution (AWS, RackSpace, Digital Ocean, etc.) However once you get big enough, the cost savings usually start falling the other way. Several companies I've been at have moved from using hosting to running their own boxes,…

Having this on AWS is perfectly fine. I even think it's viable to look at Hyper.sh as an alternative to Elastic Container Service, even though both are being hosted on AWS. But if it's hosted on AWS, it's important that people actually know that. If someone wants to build a highly reliable system, and they pick 2 resources -- let's say Hyper.sh and AWS ECS as the most likely candidates for that -- it's pretty important for the customer to know that both resources they're relying on are on the same service, and even possibly in the exact same data center, as that affects how effective their redundancy actually is.

Re: Hyper.sh – Effortless Docker Hosting

#53
post #46
post #40

Earlier quoted context omitted.

Having a CLI doesn't mean they are close. In Google cloud, you still work with VMs, cluster, schedulers. In Hyper, you work only with Docker, everything is container native! Per-second is perfect for Serverless, Data mining, CI/CD, etc. It is simply not cost effective to go with per hour/minute rate.

I admit I'm a little behind on Docker but I thought google provided that with Kubernetes [1]? I work with JVM and servlerless is just not worth it for the JVM (not yet but maybe someday with better AOT). Thus I know very little on instant serverless deployment. I'm sure it is useful though. [1]: https://cloud.google.com/container-engine/

Kubernetes lets you do stuff similar to this, but you still have to manage the infrastructure and the platform.

It seems like with Hyper, you literally are just deploying an image to be run in a container. You don't have to worry about configuring and managing a Kubernetes or Swarm cluster. Probably not worth it for very large companies, but for startups and hobby projects, this greatly lowers the barrier to entry.

Re: Hyper.sh – Effortless Docker Hosting

#54
"Hyper is a set of Linux kernel, init process and management tools, able to virtualize containers to improve their isolation and management in case of multi-tenant applications, eliminating the need of guest OS and all the components it brings. Hyper provides safe and fast isolated environments (virtual machines), on which portable environments (containers) can be easily scheduled. "[1]

The article[1] links to the hyper.sh site [2], as well as a github repo [3].

[1] https://wiki.xenproject.org/wiki/Hyper [2] https://hyper.sh/ [3] https://github.com/hyperhq/hyperd

Re: Hyper.sh – Effortless Docker Hosting

#55
post #5

"All our servers are built on powerful Octo-Core machines" pretty much guarantees they're using some cheaper than E5 Xeons to save money, I'm wondering if it's something in the Xeon-D line. Has anyone specifically characterized what they're using? Could be Xeon D-1540s or similar, or they could also be selling 4-core hyperthreaded E3 Xeons as "8 core".

Does the CPU model matter?

Re: Hyper.sh – Effortless Docker Hosting

#56
post #34
post #5

"All our servers are built on powerful Octo-Core machines" pretty much guarantees they're using some cheaper than E5 Xeons to save money, I'm wondering if it's something in the Xeon-D line. Has anyone specifically characterized what they're using? Could be Xeon D-1540s or similar, or they could also be selling 4-core hyperthreaded E3 Xeons as "8 core".

Edit: I went ahead and signed up for an account and made a container. The floating IP for the container appears to be an LA IP address. Their host appears to be ZenLayer, a Chinese hosting company that can apparently do co-location in LA, so while the IPs geolocate to China, it's possible they are indeed hosting in LA. The CPU is a E5-2630 v4. Original: I'm pretty sure they're entirely hosted on AWS. Given that they…

Not on aws at all.

The hyper.sh API address is us-west-1.hyper.sh, which looks like the AWS style, however, it is not an AWS address and it is located in an independent IDC around Los Angels.

Re: Hyper.sh – Effortless Docker Hosting

#58

Really like the look of this, feels VERY Digital Ocean-esque from the UI (which is awesome). As a big fan of DO I'm looking forward to playing with it! Edit: One interesting thing I've noticed is that I was charged a dollar for an IP address that I released after 1 minute and 11 seconds. I'd have assumed that it would have been by the second as well. However: fip 209.177.88.125 - 2016/11/07 16:27:08 2016/11/07 16:28:…

Hi, sorry about the confusion. We do this just to prevent abuse, e.g. per-second billing for IP.

PS: I work at Hyper.sh

Re: Hyper.sh – Effortless Docker Hosting

#59

Earlier quoted context omitted.

Looks an awful lot like Heroku.

There's some poor English and they list a Chinese office too. Probably not Heroku.

Native-English speaking Hyper team member here. We were founded in Beijing but have since spread to NYC.

Could you point me to the poor-English in question?

Re: Hyper.sh – Effortless Docker Hosting

#60
post #32

Google Cloud is not far from this. Basically instead of "hyper" you are typing "gcloud". Google Cloud is far more complicated but its tools so far are pretty good. I couldn't find how you do custom networks with Hyper. Also as a Java + Postgres shop 16 Gigs memory (L3) is just not enough. Per second also seems overkill. Google Cloud has per minute. It doesn't seem to make sense for "effortless". If you are that inter…

How could it possibly be the case that it takes longer to create a Docker image than a VM image?
Post reply on HN