Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Have you shipped anything serious with a “serverless” architecture?

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 207 posts

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#31

Post by tjholowaychuk »

awinder wrote: post #5

Cloudwatch logs have been a big game changer versus on-disk logs for us. Getting into larger clusters (and larger log files), figuring out what’s happening in log files became somewhat arduous. https://github.com/jorgebastida/awslogs for viewing / tailing / searching is a lot easier. It’s also fairly straightforward to get logs streamed through to ELK hosted within AWS, if you’re interested in that angle.

Do you guys find CloudWatch logs too slow? Even on very small apps I find searching the past few days takes minutes (5-10m), but I'm using "structured" JSON logs as well.

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#32

Post by tbrock »

cimmanom wrote: post #2

We've shipped something simple and non-mission-critical in production (URL rewriting for ad placements). It has been pretty much set-and-forget. Last anyone had to even look at it was almost 3 years ago, and afaik it's still working (our ad sales team would be complaining loudly if it weren't). For something peripheral like that, it's nice not to have to run servers for it or devote any energy to keeping it running.…

Regarding the tooling: I hated debugging Lambdas via CloudWatch logs when using them for Hustle, it drove me to drink.

I eventually got upset enough that I made a tool to stream the cloudwatch logs to the terminal and colorize, indent + nicely format json output:

https://github.com/TylerBrock/saw

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#34

Post by ronpeled »

We did. We are building our entire company: SQQUID on 100% serverless architecture. Scalability is awesome, in fact we had to do extra work to serialize some operations in order not to bring down other major corporation's server stack. Cost is a fraction of the traditional app scaling setup.

The best part is no devops needed. We use Serverless Framework. The biggest downside are cold starts for frontend response time. But this hasn't been a terrible issue as of yet. We have considered moving these 20 API endpoints to a nodeJS server which will resolve the issue but didn't have the time to do it yet.

We'll never go back. Serverless is the future.

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#36

Post by bufferoverflow »

not_kurt_godel wrote: post #29
zkim wrote: post #24

Earlier quoted context omitted.

Excellent writeup. Are you serving client web traffic (if applicable) via Lambdas? Or deploying your web infrastructure to traditional instances managed through CF?

Yes, we're serving client web traffic directly with Lambdas via API Gateway. We have no traditional instances or non-serverless components of any kind in the core stack.

So how do you store your state?

I assume DynamoDB part isn't serverless.

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#38

Post by sokoloff »

bufferoverflow wrote: post #36
not_kurt_godel wrote: post #29

Earlier quoted context omitted.

Yes, we're serving client web traffic directly with Lambdas via API Gateway. We have no traditional instances or non-serverless components of any kind in the core stack.

So how do you store your state? I assume DynamoDB part isn't serverless.

DynamoDB is as serverless as Lambda. (There are servers somewhere for both, but in neither case do you operate them.)

Re: Ask HN: Have you shipped anything serious with a “serverless” architecture?

#39

Post by not_kurt_godel »

bufferoverflow wrote: post #36
not_kurt_godel wrote: post #29

Earlier quoted context omitted.

Yes, we're serving client web traffic directly with Lambdas via API Gateway. We have no traditional instances or non-serverless components of any kind in the core stack.

So how do you store your state? I assume DynamoDB part isn't serverless.

DynamoDB is very much serverless :) I'd highly recommend to anyone remotely interested in serverless and/or databases to read the Dynamo whitepaper to get an idea of how it works: https://www.allthingsdistributed.com/2007/10/amazons_dynamo....
Post reply on HN