As soon as you tried to do slightly more than was possible with it, it become unviable to manage all of the Lambdas and you end up having to use Terraform or similar anyway. If I were doing lots of new Lambdas today, I'd probably just use a third-party Terraform module for all of it.
I summarised the pattern we were using here https://github.com/elgrove/terroir
I'm not surprised the project is dead. AWS want everyone using the CDK for Python or CloudFormation
as a project in the GitHub aws organization, it can not accept non amazon external maintainers.
as a project, it has a single maintainer, doing on average, an hr every few months.
as a result of both of those , its not able to keep up, or reach critical mass on community.
it has fallen fairly far behind current lambda feature set. for a simple throw away, its okay, but if you want to grow something or take advantage of new features in the underlying service capabilities or integrations, this is a dead end.
I filed this ticket a few years ago https://github.com/aws/chalice/issues/2067
Adjacent concern but: It also makes for unholy large Docker images to combine an entire JS toolchain with an entire Python toolchain.
Zappa is a better (more native) choice.
Terraform modules provide a decent Python Lambda experience.
AWS also has multiple semi-overlapping projects in the space. Chalice, SAM, and Powertools specifically to name a few. CDK more generally as well.
We never considered using serverless or anything else because we also have ECS services, RDS databases, React frontends, and a lot more. It requires some knowhow to get a good setup, but it's hard to imagine anyone more opinionated framework doing what we want.
https://boto3.amazonaws.com/v1/documentation/api/latest/inde...
But it's really just completely dead by now, which is a bummer as this leaves a large complexity gap between this and jumping ahead to just doing full Lambda+CDK/Serverless/Terraform setups.
Maybe I am just incredibly jaded but I can't stand all these shortcut frameworks. It just ends up locking you into an ecosystem, especially AWS, and decouples you from building technical understanding of the system where if you go down the path long enough, you have no abort button besides an entire re-build because your code is enmeshed with the framework.
Do it right the first time: build it simple & iterate as you go. You don't need to be thinking about scaling to 1M concurrent users when you have 0 users.
You should be using frameworks instead of trying to reinvent things. It takes away decision fatigue and makes it easier for most teams to follow conventions that are already established.
These magic-included frameworks are great to work with until you deviate from their prescribed path or just run out of road where the maintainers haven't gotten to that. There's really no need for a magic-included Lambda framework that makes AWS SDK calls as decorators, you are just asking for lock-in when that framework gets abandoned or you need a feature from a downstream dependency they haven't gotten around to implementing yet. If you kept it simple, you could 'just' bump your AWS SDK version and be on latest.
If you pick frameworks that are generally low 'magic', you can build your own road and it can be integrated into the rest of the application tightly. If you did this in a magic-included, it will generally be bolted on and imminently fragile to even slight framework changes (because the maintainers don't know or care about your hack).
I long for the good old days of /cgi-bin
Can't get decision fatigue if there's no frameworks or cloud shits to decide on.
Per that article, the word chalice does mean chalice, but is treated as a swear word precisely because it doesn’t have any profane association and has sacred overtones?
How then would one discuss these topics at all? Is this an attempt to wipe out all the words entirely?
Common examples:
* câlice [kɑːlɪs] (calice): "chalice"
* ostie [ɔs.t͡si] (hostie): "host" - as in sacramental bread
* tabarnak [ta.baʁ.nak] (tabernacle): "tabernacle"
[0]. https://en.wikipedia.org/wiki/Quebec_French_profanity?wprov=...
1) Get rid of this urge to find any word is used as swear word in one of 100s languages used across the world. People who are looking to get offended will get offended with certainty.
2) Over time euphemisms become dysphemisms and vice versa. So if new words are added to swear word categories surely old ones are falling off that list. One can possibly keep track and use those.
