They are actually neither. They are not a YC company and they are based in New York & Beijing!
429 karma · joined August 16, 2012
They are actually neither. They are not a YC company and they are based in New York & Beijing!
A Floating IP: https://docs.hyper.sh/Feature/network/fip.html
Could you drop a note on the forum [1] or join the slack [2] and ask there?
You can do exactly the same with Hyper. Play with Docker locally and then move to Hyper.
The CLI commands are pretty much identical, docker compose works in the same way.
Of course it's not exactly indentic, neither is a vagrant image and an AMI.
Outside of that you're limited to specific stacks.
Could you point me to the poor-English in question?
You could apply a similar argument to Digital Ocean or other providers. It is feasible that you could outgrow any provider, but in practice they would be able to scale before you hit that problem.
Is that what you meant or did I misunderstand?
With Hyper this is abstracted away which has a few benefits. Hyper also runs on HyperContainers (https://docs.hypercontainer.io/) which provides secure (VM like) multi-tenancy with container agility.
It's like moving Jenkins towards a static website model where you can always get back to a known state quickly and easily.
At hyper.sh we've been working to take this a step further by providing fast starting (couple of seconds), secure and highly-parallelized on-demand CI worker nodes.
We started with Buildbot (released yesterday: https://blog.hyper.sh/serverless-ci-hyper-docker-integration...) and the Jenkins plugin is coming up next.
That makes a dream situation whereby you have a Jenkins master that can be easily restored from version control and all workers are created on-demand and billed per second meaning that there is no worker node maintenance at all and you only pay when you're building.
We're calling it 'Serverless CI'. Would love to talk to you about this further. You can find contact details on the website if interested!
Clearly yours is currently lower than that.
Does that mean you've stopped using Mongo altogether?