adjohn

Fixed, thanks for the heads up!

We're happy users of both Serverless Framework as well as SAM (AWS). Serverless Framework offers a pretty rich set of plugins which provides a lot of extensibility out of the box including function warming, webpack, instrumentation and many others.

Shameless plug alert: we also dogfood IOpipe, our own dev tooling for Lambda. IOpipe[1] gives us near realtime errors, logs, tracing, and CPU/mem profiling capabilities that we're used to having in "traditional" development environments.

[1] https://www.iopipe.com/features

IOPipe | https://www.iopipe.com/jobs/ | Remote (USA) | Full Time

At IOpipe, our vision is to eliminate risk for developers and operations teams building serverless applications by providing developers with best-in-class tooling to develop, debug, and monitor their applications.

Open Positions:

* Full-stack JavaScript Engineer * Site Reliability Engineer (SRE) * Solutions Architect

IOpipe | Solutions Architect | Remote First - US Only | https://iopipe.com

We're bringing visibility to serverless applications built on AWS Lambda. With tools such as profiling, tracing, metrics, errors, and logs, we are making development faster and easier. We help developers get back to writing code.

As a solutions architect, you'll be responsible for educating prospects and customers on serverless best practices. Giving demos of how to best instrument, monitor, and observe serverless applications. Helping with integrating our open source libraries into customer's code, and creating content to help enable companies to move to serverless. As well as helping our customers with education and best practices around serverless architectures.

We're backed by top VCs, we're fully remote, and are a leader in the serverless space.

Interested? Email adam@iopipe.com with any questions.

The cold start times have been quietly getting better over time on AWS Lambda. I just checked some python Functions and I'm seeing cold starts take around 80ms on average for a simple function.

Limebike now has electric assist bikes[1] scattered throughout Seattle which makes climbing those hills a breeze.

[1] http://www.limebike.com/electric-assist-bike

Hi, I'm on the team that created this lil bot. We're happy to answer any questions about how we built this. :)

If you're in a rush, IOpipe[1] already has Python support offering profiling, tracing, and other debugging and observability tools for AWS Lambda. Co-founder of IOpipe here, feel free to ask anything.

[1] https://www.iopipe.com

I second this! TripMode is a great product if you frequently tether with your phone, or connect to wifi networks with limited bandwidth (airplanes).

It's CPU only for now, but we'll be rolling out memory dumps soon!

Great points! We'd like to expand on this to go deeper, and these are great suggestions.

Servers.lol was a side project for us to figure out if some of our own workloads were a good fit. Our day jobs are to build tooling for serverless applications. You can find more at http://iopipe.com

If you click on the "Share results" button it will generate a shareable URL for you.

It's the total number, sorry for that not being clear. We will make some improvements that may help clear that up.

Point well taken, we'll iterate on this and add some background on Lambda.

Thanks for the feedback! You should be able to edit the inputs by clicking on the left hand side (application name) to change the inputs above.

A little over a year and a half ago, we started diving deep into the serverless space. We spoke to many users of AWS Lambda and found that the biggest issue with building complex serverless application was a lack of visibility and instrumentation.

It's difficult to know when issues start bubbling up, and relying on so many services as part of your application can be scary. We've built a set of tools to help dig deep into functions, and view outwards by tracing triggers and external calls performance and metadata surrounding it.

I'd love to hear more from Lambda users about their experiences building and operating serverless apps.

IOpipe | Frontend Design Engineer | Fully Remote - US Only | $90k - $120k + Equity | https://iopipe.com

IOpipe is building a platform to help develop and operate serverless applications. We are a fully remote, venture backed team of 8, based in the US. Looking for design oriented front-end engineers to work on a realtime dashboard that makes sense of millions of events per day, per user. You'll be working with react, and a gql API.

Apply with CV to hiring@iopipe.com

Not trying to be spammy here, but I want there to be awareness that there are startups working on tools to address these gaps. Our startup, IOpipe[1] is working on one set of tools to ease development, debugging, and instrumentation for serverless applications. Aside from Stdlib and ourselves, there are others working in areas like security and CI/CD as well. These are early days, and tools will soon become abundant, but at least there are a handful to try out today.

[1] https://iopipe.com

IOpipe (https://iopipe.com) | Fully Distributed | Remote (US only)

We're a seed stage development and operations platform for AWS Lambda, is hiring a backend/systems software engineer who will be engaged in developing, operating, and scaling our APIs and data ingestion pipeline. A strong candidate will have interest, if not experience, in the serverless space, observability, and AWS.

We're under 10, venture backed, and building out a diverse and fully remote team devoted to enabling serverless development and operations. You can mail us at hiring@iopipe.com if you're interested or have questions.

We built IOpipe[1] to address these issues by offering our own wrapper[2] that sends telemetry to our service. IOpipe aggregates metrics, and errors, and allows the creation of alerts with multiple rules per alert.

[1] https://iopipe.com [2] - https://github.com/iopipe/iopipe/

We did some analysis[1] on cold starts in AWS Lambda, and found that there is a cold start if there's no activity for 5 minutes, or regardless of activity, there will be a cold start every 4 hours from creation of the underlying VM.

[1] https://www.iopipe.com/2016/09/understanding-aws-lambda-cold...

I've been using Alexa and Google Home for about a month, and I have to say that the user experience with Google Home is hands down better. Having the power of Google search when Google Home doesn't know an answer is huge. Alexa falls flat without a strong search engine backing it.

I suspect an Amazon IDE is coming. They did acquire[1] Cloud 9 not too long ago.

[1] https://www.google.com/amp/www.forbes.com/sites/janakirammsv...

Thanks for the explanation, that makes sense. We wanted to see aliases as well, because it's cumbersome setting a client ID for our Lambda monitoring service.

Why aren't you using aliases[1] for denoting dev, prod, etc?

[1] http://docs.aws.amazon.com/lambda/latest/dg/versioning-alias...

Check out Digital Ocean Hatch[1]. If you're an eligible startup, you can get 100K of free credits for 12 months.

[1] https://www.digitalocean.com/hatch/

I recommend checking out https://forestry.io/

It's pretty sweet how easy it is to make a Slack chat bot using AWS Lambda. It's a great use case, since the costs are (or almost) free for this type of application.

Apex is a framework used to help build and deploy applications on Lambda. This project appears to be a way to run your own Lambda service locally. There are other projects out there like OpenWhisk[1], Iron Worker[2], Gestalt[3], and Funktion[4].

[1] https://github.com/openwhisk/openwhisk

[2] https://www.iron.io/platform/ironworker/

[3] https://galacticfog.github.io/

[4] https://github.com/fabric8io/funktion

(Edited for Formatting)