Live data from Hacker News

Serverless Docker Beta

zeit.co

171–180 of 236 posts

Re: Serverless Docker Beta

#172
A couple of questions for Zeit:

1. Once your docker container is built, am I paying to store it on Zeit?

2. How is a Dockerfile versioned? Can I update it? Or do I need to redeploy.

3. Is pricing for containers granular by time or per request to a container?

4. How can these Dockerfiles talk to each other? Is there an API or method to fetch specific url's for each container?

Looks like a great idea, am curious to try it out sometime.

Re: Serverless Docker Beta

#173
post #165

Earlier quoted context omitted.

Workers don't run Docker containers intentionally. The goal with Workers is to run with a lower memory overhead (~3 MB) and lower startup time (~5 ms) than you can get with full container isolation. This allows your Worker to run affordably in 150+ locations around the world. In many ways it's the ultimate destination for serverless, running code in a multitenant process where all you manage is your code.

Fair enough. But that's not really the same as what Zeit is providing here.

[deleted]

Re: Serverless Docker Beta

#174
post #94
post #78

Earlier quoted context omitted.

Oh, and to make this more than a simple rant/whine, some constructive suggestions that could possibly solve the problem: - Normal video with playback controls? - Add a clearly distinguishable "this is where it starts" screen. - Is there maybe a way to control playback of a gif via JS/HTML? Add a "restart" button. - Add a timeline into the .gif that shows where I am (similar to usual video player).

Make it a webm. Then you can right click from pretty much any browser and click "show controls". See Gyfcat.

iOS does not support webm

Re: Serverless Docker Beta

#176

Earlier quoted context omitted.

Even better - make it an ASCIInema which gives you all that... and the ability to record from bash and copy and paste commands !

I've not had the opportunity to use this project yet, but https://github.com/nbedos/termtosvg seems to be another nice alternative. It provides the option of using templates that have playback controls or a progress bar. Also supports copying from the "terminal" like asciinema does.

Yes, termtosvg is a really good solution to this problem!

Here's an example with a pause/play button:

https://rawgit.com/nbedos/termtosvg/develop/examples/awesome...

Re: Serverless Docker Beta

#177

Earlier quoted context omitted.

Frankly I blame the SQL DBs for the rise of NoSQL. They didn't move fast enough for this kind of environment, and stuff like Cassandra fit that need pretty well.

That's an divisive statement. I'd blame people who were unwilling to invest the time in properly modelling their data on the rise of NoSQL. Transactional consistency and data normalisation - pffft. SQL is still doing very well running things behind the scenes.

The problem is not data modelling. The problem is ensuring eventual consistency and synchronization of data in multiple datacenters around the world.

Re: Serverless Docker Beta

#178
post #73

Am I the only one having problems to follow .gif "demos"? When I get to the image, it is in the middle of everything and I don't really have an idea what is going on. Even watching it multiple times, I am not sure where it starts, ends, what the individual steps are. Or is it because I just don't know enough about this stuff?

they do explain it. gifs have there place but this may be too long for a looping gif, i believe a proper stream would have been better to display the commands and process.

Re: Serverless Docker Beta

#179

Earlier quoted context omitted.

Chromium browsers compiled without proprietary codecs require webm. It's a small subset of people (I am one), but I just don't play and/or leave sites with mp4 only.

Why is that? Are you "afraid" that mp4 have some embedded code that will run...idk I just made that up!

.mp4 videos usually use h264 compression (and now h265 for 4K/HDR), which is not free or open source. .webm uses VP8 or VP9.

Re: Serverless Docker Beta

#180
post #172

A couple of questions for Zeit: 1. Once your docker container is built, am I paying to store it on Zeit? 2. How is a Dockerfile versioned? Can I update it? Or do I need to redeploy. 3. Is pricing for containers granular by time or per request to a container? 4. How can these Dockerfiles talk to each other? Is there an API or method to fetch specific url's for each container? Looks like a great idea, am curious to try…

> 1. Once your docker container is built, am I paying to store it on Zeit?

No. You don't need to pay to store containers.

> 2. How is a Dockerfile versioned? Can I update it? Or do I need to redeploy

Once the Dockerfile is built, you'll get a URL for that. It's a immutable URL and you don't need to re-deploy again. It'll sleep if there are no HTTP requests. If there are it'll start again.

> 3. Is pricing for containers granular by time or per request to a container?

It's based on the container running time. But we'll have a another blog post on this soon with more info.

> 4. How can these Dockerfiles talk to each other? Is there an API or method to fetch specific url's for each container?

There's no internal API to communicate with each other. But every docker container has a URL. You can use our [alias](https://zeit.co/docs/features/aliases) feature and communicate with each other via HTTP.

Post reply on HN