167 karma · joined November 24, 2014
In regards to performance optimization of Lambdas, start-up time is the most important factor as cold starts happen also in cases of concurrent requests when no warm instances are available. This means that Go, Node and Python are pretty sweet for serverless. Thanks to recently released Lambda SnapStart feature that launches new instances from snapshots taken after application initialization Java (even with DI frameworks) is a plausible option if you're inclined that way. Previously you had to use a custom runtime and AOT compilation (that rules out any runtime DI stuff) to achieve tolerable performance with Java on Lambda.
- Sofa laptop running MacOS
- Raspberry Pi running Linux (RetroPie)
- SFF gaming desktop running Windows 10 Pro
- reMarkable 2
- Two Android phones (work & personal)
What a nice way to formulate the tradeoffs between cost and security. When Workers came out with huge headlines about performance and cost I was very disappointed to find out there was no special technical wizardry behind that but just conscious trade-offs in disregard to customer data security. Workers simply skip all the sandboxing steps other providers take to implement a multi-tenant application runtime in a secure manner. So far the mitigations in place seem to make the possibility of Cloudflare customers getting bitten by a V8 vulnerability unlikely instead of impossible.
Sure, the platform has interesting ideas and I'm looking forward to try it out as a full-stack serverless platform. I just cannot foresee running anything serious on it before they come up with a more convincing security story.
I don't know a better dev environment than a (possibly scaled down) personal replica of production environment in the cloud. With proper tooling (e.g. Serverless Stack or SAM) you can achieve very fast code updates so the old argument of slow feedback due to having to deploy changes to the cloud on each iteration is getting less and less true as well.
With more traditional models already keeping your OS, possible container images, web server and any other middleware secure and up-to-date is pretty expensive if you want to do it properly.
Going all-in on serverless might not make much sense for a large software product company but when building bespoke business software it allows small teams to do wonderful things very cost-effectively.
Wait, this is the first time I hear this about Azure. Could you elaborate? It is possible that things have improved significantly since I last worked with Azure but lack of a consistent security model (like IAM on AWS) to control human and service (Azure Functions, App Service apps etc) access to specific resources (Cosmos databases, EventHubs etc) especially painful.
My perspective is limited and evidence anecdotal but I've seen only one on-prem to serverless "migration" project so far and that was a complete rewrite. The original codebase was ~20 years old, had a tight dependency on an expensive proprietary database and a variety of scalability issues so it would have needed thorough rearchitecting anyway. A more common pattern is to do the lift & shift and incrementally either create new services or migrate existing ones to serverless where it makes sense (the strangler pattern).
For entirely new applications serverless solutions are usually the first option to be considered since they are very easy to operate. Many clients also don't have much expertise in-house for operating k8s so new workloads would be operated by outsourced ops teams or development teams themselves which is very expensive. Large enterprises also have formed some sort of "strategic partnership" or alliance with either Amazon or Microsoft so cloud agnosticism rarely enters the picture. In addition to being easier to operate, skilled development teams are also very fast to deliver on serverless since there's very little infrastructure-level things to worry about. The team can focus on business logic and delivering value from day 1. If you only look at Heroku I can assure you the market for serverless is much bigger and constantly growing.
Are there any plans for some kind of combo deal now that Sublime Text and Sublime Merge licenses are aligned?
My only complaint is the lack of Linux support for the app that allows mirroring the screen to a computer. Would be really cool for sketching stuff during online meetings.
Static cost of data streams come up in data projects but even there it's trivial to consume data from shared streams in developer-specific environment since the stream pointer is managed in client side. The throughput required by even multiple occasionally consuming dev environments rarely requires provisioning streams above minimum capacity.
DynamoDB in on-demand mode is my go-to OLTP database until I know enough of runtime load characteristics to provision static capacity with autoscaling. For any non-prod (or load testing) environment on-demand mode is the best choice. Aurora Serverless is OK as well but has its warts and so far the cases where I really need a relational database in a greenfield project have been few and far between. Anything with complex query requirements goes to S3 and gets queried asynchronously or in batches via Athena. Not suitable for real-time cases though.
Things like queues, notifications and e-mails are handled by SQS or SNS and paid per usage. Websockets by API Gateway and Lambda.
Architecting for serverless requires a shift in mindset and tooling but as a benefit you get cheap isolated development environments and truly elastic production environments with very little ops burden.
One of the results of the pay-per-use pricing model of services utilized in serverless architectures is that you can easily provision dirt-cheap developer and feature-branch specific environments for integration-level testing. While you still can't attach a debugger in your function, the isolation from changes others are working on makes testing and exploration much more pleasant than when working in a shared dev environment. Things only get complicated when your architecture includes more expensive components with different pricing schemes that you probably want to share with others (e.g. relational databases, data streams).
If you're into Lisps the Racket GUI library is really nice and actually looks like the easiest option for developing native GUI applications with capability to build for different platforms.
If the you're targeting Windows only then .NET + C# is probably the best alternative. Not the easiest platform to learn but you'd be learning skills that have more demand on the market.
Minesweeper is such a cool exercise when learning new stuff. A co-worker challenged me to write this crude implementation on a flight from Heathrow to NYC while I was learning Go: https://gitlab.com/joyey/kakkamiina
Serverless applications' reliance on other proprietary services like Cognito, DynamoDB etc is another thing however...
We have one service running that consumes data to a Kinesis stream published as an API GW endpoint. Preprocessing is done in Lambda in batches of 100 records and the processed records get pushed to Firehose streams for batched loads to a Redshift cluster for analytics. So far we've been very happy with the solution - very little custom code, almost no ops required and it performs and scales well.