#LambdaLiterary made a very considered, well-written press release saying (basically) ‘genocide is bad’. This has made a lot of queer authors very, VERY angry.
Imagine being a queer author in 2024 and having the audacity to be angry that a queer author group makes a political statement. In 2024.
Imagine being a queer author in 2024 and telling a queer author group to (and I quote) 'stay in your lane'.
It appears my university newspaper #Lambda, where I got my journalistic and political beginnings is no more, having been affected by Doug Ford policies and going online only in 2019, the latest post on the online edition is from September 2021 and the latest archived version is from September 2021.
I have ses receive mail and put it directly into an s3 bucket.
Bucket has a notification to topics for creates into the report and forensic subfolders to a sns/sqs that feeds the lambda to process them. Then I can batch them.
Then lifecycle policy on bucket to clean up reports.
After one year of doing micro services in #kubernetes , I don't like it. It's very complex, it's hard to add new services that need to talk with other services, managing tokens and such. The data flow is complex. Maybe we're doing this wrong...
This year it will be a monorepo, in a #lambda. It's cheap, it's scalable, it's simple. Old micro services will become a library.
I've just started learning #webComponents and oh my days there seems to be a lot of ways to boilerplate this. Should I just use #Lit? It looks like I'd need a bundler which seems overkill for my tiny #11ty site.
I wrote a blog describing how I translated a feature request into a #cloudnative#eventdrivenarchitecture, where the events we're interested in convey nothing happening for a certain amount of time.
But before I arrived at my current solution, I considered other solutions. I describe those as well, and explain their shortcomings.
It involves #AWS#DynamoDB, DynamoDB Streams, and #Lambda (#kotlin), with some #DDD context mapping considerations thrown into the mix.
Custom Bash Runtime for Lambda Container
~~
ACM.305 Using AWS base images for a container that runs a custom Lambda runtime
~~ #bash#container#lambda#runtime
#Othello front end served by #Apache, written in #JavaScript with #Phaser 3 game engine, back end served with #Flask (soon AWS #Lambda) and written in #Python. There's a lot going on but it sorta works. This proves my idea to offload the processing to a remote back end driving a thin client works.
It plays terribly at the moment, but it's good enough to work on the UX.