gnepzhao
Joined 12 years ago
Joined 12 years ago
Think about why all public clouds are built with virtualization technology. Multi-tenants require strong isolation, which virtualization promises. Therefore, if we could get strong isolation in container, we can build public cloud with container.
Disclosure: I work at Hyper.sh
Part of the reason we chose to open source is that we want the community to innovate. We are continuing to build the feature set, however I need to say that the workflow varies from app to app. Therefore, by providing the base building block and allowing others to create different solutions, we could enable more options to the market.
I'm one of cofounders of Hyper. Thanks for mentioning us!
I think both ECS and GKE are valid options their segment. Things like ACI and Hyper.sh is more of a container-native IaaS. The on-demand event-driven compute infra is a perfect use case, but it also works for long-running workload (k8s pool), where the difference is that developers only need to consume the k8s api, not the software itself.
The vision is to merge PaaS into IaaS, e.g. a microservice-native cloud. I want to ask more details of the upper-layer features you imagine. Thanks!
I'd like to keep in touch. Could you drop a message to peng at hyper.sh? Thanks.
Kind of similar to LB+ReplicationSet in K8S, not automated scaling yet. But will do.