TIL that when you manage #AWS Step Functions using #CDK or #CloudFormation, you have no control over JobDefinition revisions. So whenever you change a job definition, CloudFormation creates a new revision for it and inactivates the previously active one.
So in practice, when you update a StepFunctions job definition any existing long-running executions that depended on the old version will simply fail. And waste a ton of resources and potentially money.
This sort of problem is exactly what turns some engineering leaders off of #serverless for other architectures.
In particular, I wish AWS would spend more energy into making CloudFormation support better across the board. Like requiring support for new services and ensuring a minimum resource coverage as part of service teams' goals. Because it doesn't look like this is the case today. Something many people like @Quinnypig have been screaming (in the cloud) about for ages now.
Sorry for the rant. I like AWS and serverless, but this boiled my blood today because it had non-trivial impact into my operations and cost and took the team quite a while to figure out. Now we'll have to figure out an ugly workaround to implement. 🙄
"Everything should be a #serverless function" is just as shortsighted as "Everything should run on Kubernetes" or "Everything should be a #monolith". There is no one-size-fits-all #architecture. Every setup has, or will have, shortcomings. When a new tool arrives to address such a shortcoming, it doesn't mean you can just apply that tool preemptively to every problem to avoid any and all shortcomings. Maybe cold starts aren't an issue for you, or you don't need to scale horizontally.
I am starting to miss the "hide reply" option from #Twitter. Some of my toots attract reply-guys with their typical negativity that I would really like to remove from some threads to keep the positivity of other replies alive. UPDATE: Or implemented as a Content Warning style option (“Hidden by thread owner/curator”) where the reader has to consciously click to reveal the content.
@DrArtAnalytics Yes. I feel responsible for „my“ threads and as I also use threads as a #serverless way to add comments to my blog and other static pages (see https://jan.wildeboer.net/2023/02/Jekyll-Mastodon-Comments/ ) I’d really like to be able to moderate. And I’d be perfectly fine with an implementation that allows the reader to still open the hidden reply, if he/she/they wish to do so instead if it not showing up at all. Kinda like a content warning by the thread „owner“.
Hi, as a #FunctionalProgramming beginner, I'd appreciate any guidance. Links to in-depth discussion, examples, and summaries would be great. I'm pretty fine with #JavaScript overall, and have used some FP features, but strict FP is new to me.
To understand them better, I will not stop with just reading and documenting, but might write a app (server, client, bot) to solidify my understanding.
There are different approaches to developing apps for #fediverse
• a typical mastodon app implements both front-end and back-end
• #gotosocial type of apps implement only backend api (along with cli all in #Golang )
• apps like @sengi_app are only at the front-end
• @brianmmdev is implementing a fediverse app via #serverless model
As mastodon picks up steam, we will see different types of apps
[Fixed Now] Outage of Amazon's cloud service causes some websites to go dark (apnews.com)