Down for me.

Tangentially related question. What deployment tools are people using to manage systems with many lambda functions?

We use SWF to trigger over 50 separate lambda functions in processing. We've got some very nice internally developed tools to identify which functions are out of date and help with deployment. I'm just curious what else is available to handle DevOps tasks in a Serverless environment (i.e. deploying library updates, etc).

I'm not aware of a publicly available tool that does this (without bringing in a big clumsy framework), but internally we just use a script that idempotently redeploys all the lambdas by calling update_function_code on them. It ingests package dependency changes by running "python setup.py install" and grabbing the resulting site-packages contents. This script can be subscribed to an SNS-SQS bus that listens to GitHub notifications for changes on a branch, etc.

This will flush hot lambdas, so if you have a lot of traffic it can be a bit disruptive. I can imagine comparing deployment and commit timetamps make-style, or calling update_function_configuration(Description=...) to save and later compare version/commit metadata.

AWS recently came out with https://github.com/awslabs/chalice, which is pretty sweet if you're using Python (although it doesn't seem to directly address the concern of deployment orchestration).

I've looked at chalice very shortly, and it was really nice to easily set up an API Gateway -> Lambda connection, we haven't really looked at it for our non api-gateway uses.

I've only heard of Apex: https://github.com/apex/apex

The rtl-sdr dongle is available for around $25 on Amazon.

$8.66, and I'm sure you can go lower. https://www.amazon.com/DVB-T-RTL2832U-RTL-SDR-Receiver-Compa...

Anything with RTL2832U + R820T will do.

Came to post the same thing. Don't get too hung up on the actual database, just learn SQL and relational databases. It's something you will use over and over again, even if it's just to peek into the back end to see what your framework, ORM, etc actually did with the data.

I do this too, If I'm saving the file for reuse, I wrap the entire thing in /* */ when I'm done just in case I accidentally hit run script instead of run statement.

FBReader has an decent interface for searching, but you need to know what you are looking for. There's not a good way to browse via the app.

I'll second FBReader; works great on my N900. Though you do have to have your library organized outside of it, it doesn't browse well.

I've been trying to beat this into the skulls of my employees. I run a contract based QA team so there's a good chance our paying client(s) are going to see everything we have entered into their databases.