Live data from Hacker News

Serverless Docker Beta

zeit.co

111–120 of 236 posts

Re: Serverless Docker Beta

#111
post #64
post #48

Earlier quoted context omitted.

Yup. I’ve seen this - customers who insist every package has to be installed in some special place because /opt is ‘reserved’ - have to have non-standard ports for everything because it might slow down attackers - have to have an Apache proxy in front of everything, always - even internal components. ‘Cos. - won’t invest in trusted SSL certificates for internal services. - every sql query has to be wrapped in a store…

There is actually a reasonable arguement for the stored procedure one. It means you can have different permissions for tables as you do for stored procedures so your application doesn't have permission to directly query your passwords. The benefit there is if an attacker gains access to your application and/or the DB authentication credentials they cannot then export users passwords or other sensitive information.

Seems more efficient to me to use column-based permissions in this case, and create stored procedures for the queries you need to interact with the "sensitive" columns.

That of course does increase (dba) administration overhead, but it seems on it's face simpler and far more "programmer efficient" than storing every single query as a stored procedure.

Re: Serverless Docker Beta

#112
post #97
post #94

Earlier quoted context omitted.

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

You can view controls on GIFs in many cases as well, I believe. Also, nobody seems to make use of these features, but GIFs do not have to loop, nor do they have to loop by going back to the very beginning of the animation as well. In particular, I find it extremely ineffective where there are GIFs that only show a "final product/scene" for like 1 frame before looping back to the beginning.

> You can view controls on GIFs in many cases as well, I believe

I don't think that's true.

Twitter and imgur do convert gifs to mp4, and you can see controls there, but that's because they're not gifs.

Do you have a citation or example of controls on actual gifs in any commonly used web browser?

Re: Serverless Docker Beta

#113
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.

WebM is not supported on Safari (OSX or iOS) and is listed as only partially supported on Edge.

https://caniuse.com/#search=webm

Re: Serverless Docker Beta

#114
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?

Totally feel you on this one, especially when the purpose is to inform/teach. I found this extension that helps: https://chrome.google.com/webstore/detail/play-the-gif/mchec...

Re: Serverless Docker Beta

#115
post #35

There is no 'hype' word in history I hate more then serverless. I was fine with microservices and all those other hype words but serverless is terrible.

mind elaborating a bit?

There are still servers involved. Serverless sounds like its peer to peer. What it really is is VM less.

Re: Serverless Docker Beta

#116
post #40

And so ZEIT, my favorite serverless provider, keeps getting better. Highlights: - "sub-second cold boot (full round trip) for most workloads" - HTTP/2.0 and websocket support - Tune CPU and memory usage, which means even smoother scaling And all that for any service you can fit in a Docker container - which is also how you get near-perfect dev/prod parity, an often overlooked issue with other serverless deployment te…

I'm not a "serverless hater", but every company I've ever worked with had backend processes that were not tied to HTTP requests. I still keep actual servers around because the HTTP gateway is not the pain point. It's long-running processes, message systems, stream processing, and reporting. That said, I look forward to the company (or side project) where "serverless" can save me from also assuming the "devops" role.

Functions that respond to events, where an event is triggered by some sort of message queue (ie, Lambda + Kinesis streams)

Re: Serverless Docker Beta

#117

Earlier quoted context omitted.

Until you discover that the thing you are building requires more than a single application running in a single container and you end up building an entire "Operating System" around your containers and the circle starts all over again. Complexity is hardly ever in the solution, but mostly in the problem. Single solutions to complex problems often ignore/forget important parts of the problem and they come back to bite…

I don't know... My experience is the other extreme - tech teams that make everything super complicated to support everything that can possibly happen. As a consequence, the it environment requires six months of experience to even understand. It's really not very fun to work in those environments. Lots of unnecessary complexity.

I have the same experience and I'm on both sides in my day job. On the one end preventing developers from having to make the same (learning) mistakes that have already been made by ops so they can focus on developing and delivering, stuff like HA, security, backups, networking, statefulness, etc. Just deploying you apps on containers doesn't solve these problems.

But on the other end I'm constantly fighting the complexity of existing environment and preventing to much new complexity being added. It seems that every time a new tool/product is introduced which makes things simpeler, it just end up being a Hydra and total complexity is only increased.

I still have to find the holy grail if there is one, some middle ground? Or maybe it's just human nature to always make complexity where there is none since "It can't be that simple, can it?".

Re: Serverless Docker Beta

#118
post #46

Earlier quoted context omitted.

I think all that is still possible in Serverless. I'm not a serverless architect or anything, but that's typically handled by various serverless queues and related event systems.

Don't most serverless calls have a time limit?

Yes, but you typically build your functions to split up the work if necessary. (Create additional queued events)

Re: Serverless Docker Beta

#119
post #79
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?

I share your pain. Need an extension that would add playback controls to gifs, or at least "play from beginning"

here https://chrome.google.com/webstore/detail/gif-scrubber/gbdac...

Re: Serverless Docker Beta

#120
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?

[deleted]
Post reply on HN