121–130 of 218 posts
https://docs.hyper.sh/Reference/CLI/service_rolling_update.h...
Hey all, founder is here. I'd like to thank you for your votes here. Really appreciate! Also, I just want to share our public roadmap: https://trello.com/b/7fEwaPRd/roadmap . Feel free to comment. It actually helps a lot for us to prioritize. Thanks!
Earlier quoted context omitted.
It's almost the same as using docker locally.
Okay, but that doesn't answer my question. :-) I'd like to run a local instance of the "hyper system," fully contained on my laptop, perhaps running atop virtualbox. If I find it appealing, with respect to the usage experience (i.e. deploying/composing containers), I'd be willing to run some apps on the real deal. I am, though, not willing to experiment with the "real deal" as a means of evaluating it.
If you think you might end up using it, why try and replicate it on your machine (any more than Docker already does) rather than just cross the deployment bridge sooner?
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…
For long running containers, true. But I want to manage some of my data processing as a bunch of individual components that may have very short runtimes. I don't feel like paying for 10 minutes as a minimum makes sense if I only need a machine for 90s.
Their recent examples of using it as a highly parallel build server make more sense there. Do you want to pay for 10 minutes every time you trigger a 1 minute build job?
Earlier quoted context omitted.
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 importa…
I signed up for the trial and was pretty impressed how easy it was to get up and running. I'm hesitant to use for production-level workloads. As it matures I think it will be a great platform (and then Amazon, Google, or Digital Ocean, etc. will acquire it and maybe roll it into their offerings or maybe kill it.)
Earlier quoted context omitted.
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.
There is a separation of concerns slowly baked into Kubernetes in that as a normal user you shouldn't need to manage the infrastracture.
Hyper allows for the creation of a minimum viable product that you can move around. I can start on Hyper and then move to pure AWS/Kubernetes/mesos/swarm when and if I determine it makes sense to have people spending time managing the AWS infrastructure and handling deployments.
I haven't used Hyper, but this idea is really cool in principle. I'm excited to see how well they actually do it. It really seems like the Heroku of containers.
Is there something like this on top of DigitalOcean/AWS instead? I'd rather rely on those providers for the hardware and uptime.