A deep analysis of AWS Lambda Cold Start latency for 2020.
Cold Start is much much better, but is still an overhead that needs to be factored in.
I learned that “Cool” Starts are a thing and that different can have dramatically different performance profiles.
A discussion on AWS pricing. Once your start scaling, you have to be pushing some quite serious dollars through AWS to justify spending any real time on reducing costs. Learning to manage costs early is a massive benefit as you scale.
Corey Quinn is brutally insightful (as always) on the lies we tell ourselves (and others). …
I predict that we’re in a post “flexibility” world.
In practice, flexibility boils down to “come in a bit late”, “leave a bit early”, “work from home if the repair person is coming”.
Flexibility is necessary, but it is not sufficient.
The pandemic has shown that nearly everyone can work from anywhere at least some of the time.
Our practices probably need to change. “Zoom fatigue” is a symptom of lifting and shifting existing inefficient meeting-driven work practices to video conferencing. We’re not having more meetings, we’re just suddenly aware of how many meetings we have.
Regardless of our physical distance, we have an incredible moment to change our work practices for the better. We can encourage ways of working that are reflective, considered and asynchronous. Collaboration around shared artifacts that enhance shared understanding. Communication that embraces the asynchronous — written and recorded explanations and summaries that have a lifetime outside of the moment. …
Adopted from this post on Hacker News https://news.ycombinator.com/item?id=15777442
Randomly infrequent tales of interest from the cloud mines.
A collection of common patterns for microservice architectures.
Some people are apparently going to run their own serverless systems and Open Whisk on Kubernetes is the main player. I think this is a ridiculous approach, but it’s an interesting counter point to my biases.
Also, Open Source really is the only play against AWS.
A great overview of the major players and the capabilities of the various platoforms in the FaaS space.
Useful for screenshots or replacing your CI infrastructure with a series of Lambda functions.
Detailed analysis of using X-Ray with Lambda.
I ❤ you Postgres.
An example of using Kafka Connect to consume writes to Postgres and automatically send them to Redshift.
Automatically examine slow queries and build indexes.
Also, you may be amazed to read about Hypothetical Indexes for Postgres that make all of this possible.
Tales of interest from the cloud mines.
I like feature branches, but this deck is spot on. Long-lived branches are going to hurt you.
The machines are coming.
Because of course:
If you can’t build a well-structured monolith, what makes you think microservices is the answer?
The biggest change I see in tech is that the barrier for entry to microservices has been lowered immensely:
1. Rapid provisioning
2. Basic monitoring
3. Rapid deployment
Any one the FaaS platforms will provide all of the above (with the caveat that you might find the basic monitoring pretty basic indeed). …
Periodic tales of interest from the bit mines.
The next time you start to write a log line, ask yourself whether another observability tool would be a better fit.
Not everything should be a log, performance and error information can be pushed to specific tools.
Also, debugging Lambda via console.log is totally a thing, and it’s hard.
The only way to gain confidence that a feature branch will work in the cloud is to run it in the cloud. …
This was a tweet thread that became unwieldy.
I could be doing things very wrong, so feedback to improve is very welcome.
I write a lot of tests. My advice for everyone working with serverless platforms is to try and side-step the need to debug in “the cloud” as much as possible. Small functions with concise, testable interfaces. Nothing to see here, it’s all programming.
Even with good tests I still find that I often end up resorting to console.log to understand the flow of events through the system.
Add console.log statements, push, trigger an event, dig around in CloudWatch to find the log. …
Tales of interest from deep in the Bit Mines.
This week I have been mostly playing with Lex in my spare time because I plan to win the AWS Chatbot challenge.
Testing, itself, is complicated, because tests are techno-social constructs that support both the code and the team that works on it.
Why do we even write tests?
A high level overview of the AWS Security surface.
From my experience, customers spent most of their time securing their network because they know how to do this. I recommend that you shift your resources a little bit to make sure you get the AWS API Security right. …
Tales of Interest of the Computing and Clouds
Functions as a Service as a Language:
FaaSlang is a simple open specification intended to define semantics and implementation details around FaaS (“serverless”) functions, gateways and client interfaces (requests from any language / SDK).
Interesting idea, especially as more open source projects jump into the FAAS space. However, vendor lock-in remains a fairly moot issue because a whole lot of serverless as a model is tied in with platform-level events. Hard to abstract elements like kinesis.
How will you transform your organization from a feature factory to a product laboratory?
An analysis of how serverless tech can actually make your process more good. …
Being an account of some things that captured my interest over a recent period of time.
TL;DR They save a bunch of money through:
Working with Kinesis and Lambda
Overview of converting a monolith into a AWS Lambda and friends based serverless application.
Biggest take-way ‘Optimize for Concurrency’. Lots of small, short-running functions.
Databases haven’t really changed since the 80s
Why don’t modern databases simply provide these features? I don’t know. I can guess, but I wont be charitable. Because its hard. Because modern web apps are too new, and server rendered apps look too much like the old desktop apps to give anyone pause. Because database developers don’t write frontend code. …