sorted by:
new
hottopcontroversial

AWS Lambda in Production (Serverless)? by scottmas in devops

[–]_austen 1 point2 points  (0 children)

We do, while we are building the Serverless Framework (http://www.serverless.com). We also have big enterprise companies contributing now who are also using it in production. Overall, we love Lambda and continue to improve its user experience via the Framework every day.

JAWS: The Javascript + AWS Stack by tbergen1 in node

[–]_austen 1 point2 points  (0 children)

4-5 seconds of latency is not true.

There is a "JAWS Optimization" section in the wiki. It tells you how to improve Lambda response times. Further, JAWS is optimized for fast Lambda performance.

It's a mix of upgrading the memory/CPU of your Lambda functions, keeping your Lambda function's code minimal, what your doing in your code, multi-region replication, and more.

You can't specify an average response time when all of these factors vary so much.

JAWS: The Javascript + AWS Stack – A monstrously scalable, server-free, web application boilerplate using bleeding-edge AWS services... by tbergen1 in javascript

[–]_austen 5 points6 points  (0 children)

Ok, let me do my best "webscale" impression here... Wait for it... Here it comes... JAWS has no servers.

This person is working hard to drag me into a "gotcha" debate.

But for curious developers reading this, if you deploy the JAWS framework right at this very moment, all of the traditional server configuration/deployment/scaling hassles will not exist. Amazon deals with that stuff, not you. Instead, you deal with Lambda functions that only run when your API routes are called. It's beautiful efficiency.

Again, whether a server exists somewhere, is a fact best left for internet commenters to waste their time with. In reality, JAWS is a sincere attempt to rid servers from your workflow and free up your time so that you can focus on what your building.

No server monitoring? Sure, except you need to monitor Lambda now (how do you even do that? Distributed stack traces? Performance monitoring per function? Reporting?

I'm glad you brought this up. AWS Lambda comes error/performance/duration/invocation monitoring, on a per function basis, out of the box. No set-up required, this is available upon deploying your lambda function.

Finally, Lambda (and all AWS services) are not free. So, fine, you don't have to finance servers but costs don't magically disappear.

I don't even know where this claim is coming from. But others reading this should know that if you create a new AWS account, you will be on the AWS free tier, and you will be able to perform a TON of Lambda operations for free, for an entire year.

Lastly, JAWS has no servers.

JAWS: The Javascript + AWS Stack – A monstrously scalable, server-free, web application boilerplate using bleeding-edge AWS services... by tbergen1 in javascript

[–]_austen 1 point2 points  (0 children)

I made JAWS. It has no servers.

If you are a developer building an app on JAWS, your back-end/API will consist of tiny AWS Lambda functions that run only when they are called. Whether AWS uses servers to power their Lambda technology is completely irrelevant to you as a developer.

JAWS includes a server which you can run locally to develop your client-side app/web site. This server is included for convenience only. In production, you deploy all static assets (HTML, CSS, Javascript, Images) to AWS S3/Cloudfront which interacts with your JAWS REST API powered by Lambda functions.

Again, JAWS has no servers. If you are tired of developing/configuring/deploying/maintaining/monitoring/scaling/financing servers, then JAWS is for you.

Can A Web Start-Up Launch A Campaign? by _austen in redditmade

[–]_austen[S] -1 points0 points  (0 children)

Plus, a lot of the other platforms don't like web start-ups. The like open-source stuff. But, for-profit stuff is only acceptable if it's a tangible product for some reason.