Regarding programmatic endpoint handlers, these solve completely different problems. Different to the point that there's no reason that you can't employ one on top of the other.
When you start hitting endpoint limits there's a very strong sign that you've had responsibility creep for a microservice, or even worse you're treating your serverless deployment as a monolith.
Your insistence on integrity issues with DynamoDB is also strange. Religious adherence to ACID is not going to be your silver bullet for application design. Learning how to reason about distributed systems and their eventual consistency is necessary to begin with in most cloud setups.
Anything you can do with serverless can be done better with k8s? Cool, have it provision my underlying infrastructure
"Religious adherence to ACID is not going to be your silver bullet for application design. Learning how to reason about distributed systems and their eventual consistency is necessary to begin with in most cloud setups." So you just X10 the development costs for no good reason. Also as a user of many FANG services that are using eventually consistent stores color me unimpressed by the user experience. Considering that a startup or even a F500 company has a pretty low chance of hiring people of the same caliber as those systems were designed by this is nog a good solution for 99% of the projects.
I cannot fathom the process through which one arrived at that file. It started out looking like someone who did not know that shell scripting was a thing, only to morph into a golang program writing out a shell script and exec-s it: https://github.com/bbelky/hkube/blob/master/hkube.go#L193
The icing on the cake is committing a compiled binary for some unknown platform into git
When you start hitting endpoint limits there's a very strong sign that you've had responsibility creep for a microservice, or even worse you're treating your serverless deployment as a monolith.
Your insistence on integrity issues with DynamoDB is also strange. Religious adherence to ACID is not going to be your silver bullet for application design. Learning how to reason about distributed systems and their eventual consistency is necessary to begin with in most cloud setups.
Anything you can do with serverless can be done better with k8s? Cool, have it provision my underlying infrastructure