Serverless Docker Beta
zeit.co
Serverless Docker Beta
1–10 of 236 posts
Re: Serverless Docker Beta
#2Yep. Pretty soon. You write code. You create a docker file. You find a place to run the docker file with your code [cheapest!]. Run it through your tests. Monitor it. The end. No vpcs,salts, puppets, sshs,chefs, horses,anisbles, cats,ec2s,devops,noops, sysadmins, kubernetes or chaos monkeys required.
Re: Serverless Docker Beta
#3My biggest problem with serverless functions is development and testing. Can I run these locally? even better offline?
Re: Serverless Docker Beta
#4I did not play with it, but this actually looks pretty cool. The documentation seems to be sane/good quality.
A few questions: How would one coordinate between multiple nodes running an app? (scenario in which the nodes cooperate to find each other. is there some sort of discovery available?) For the docker case, does it support health probes? (how you you know if the app is healthy?)
Re: Serverless Docker Beta
#5My biggest problem with serverless functions is development and testing. Can I run these locally? even better offline?
AFAIK at least AWS Lambda has a Docker based CLI that lets you run functions locally.
I guess since the Zeit solution is based on Docker something like this should also be possible...
Re: Serverless Docker Beta
#6Looks great for basic websites but it's missing the biggest and most difficult piece of cloud infrastructure. The DATABASE!
Today you'd have to open up your cloud DB provider to the world since Zeit can't provide a list of IPs to whitelist. This is a showstopper for me unfortunately.
Re: Serverless Docker Beta
#7I did not play with it, but this actually looks pretty cool. The documentation seems to be sane/good quality. A few questions: How would one coordinate between multiple nodes running an app? (scenario in which the nodes cooperate to find each other. is there some sort of discovery available?) For the docker case, does it support health probes? (how you you know if the app is healthy?)
For the duration of the warm phase (i.e.: while the process is running), we ascertain healthfulness via `SYN` packets as a baseline.
Because you give us your code under the constraint that it will expose data over a port, we have a much better safety baseline than stock schedulers, that operate under the assumption that the process describe by `CMD` is a black box.
We will describe this in more detail in coming weeks. One of our priorities is to minimize the cognitive load on the developer necessary to run a healthy service at scale.
Re: Serverless Docker Beta
#8Yep. Pretty soon. You write code. You create a docker file. You find a place to run the docker file with your code [cheapest!]. Run it through your tests. Monitor it. The end. No vpcs,salts, puppets, sshs,chefs, horses,anisbles, cats,ec2s,devops,noops, sysadmins, kubernetes or chaos monkeys required.
this wont be popular but I always felt like docker was a step backwards in order to regroup and take a giant leap forward.
I went from right clicking and deploying from visual studio to SSH and configuring dockerfiles, docker compose, even nginx.conf to loadbalance.
You do get more bang for the buck with such setup but its too much work on infrastructure and less time for development.
edit: add kubernetes to it, although AKS and GKE being free lessens the burden its still too much for a software dev like me.
Re: Serverless Docker Beta
#9My biggest concern with serverless is pricing. How does it fare when compared to regular Docker hosting and vps hosting?
Re: Serverless Docker Beta
#10My biggest problem with serverless functions is development and testing. Can I run these locally? even better offline?
AFAIK at least AWS Lambda has a Docker based CLI that lets you run functions locally. I guess since the Zeit solution is based on Docker something like this should also be possible...
ah, I didnt know that. I assume you mean this? https://github.com/lambci/docker-lambda