3 ms·
Moving from Serverless to Functionless
- frenchtoast8 11mo agoLink should be: https://builder.aws.com/content/2bS1CDz7CcbNkHEemEWOcZkUuel/moving-from-serverless-to-functionless https://builder.aws.com/content/2bS1CDz7CcbNkHEemEWOcZkUuel/...
- smitty1e 11mo ago"We've made fat piles of cash off of dysfunctional software for decades," said Micrsoft.
- knowitnone3 11mo agoCan't wait for loopless
- SwiftyBug 11mo agoWhat do you mean? You can already do loopless! Just send events recursively. AKA functional functionless architecture.
- moltar 11mo agoI do really like this step function pattern especially with the new JSONata flavour it’s much more approachable than the original DSL that was so painful to write and debug.
- mlhpdx 11mo agoWhen it first came out the developer experience was awful but it’s come a long, long way. JSONata is definitely a big part of that, along with the workflow designer being available in VS Code and tolerant of placeholders (${Foo}). The article’s callout of direct service integrations in API Gateway is also spot on. When they can be made to fit, they’re such a nice way to go.
- squiffsquiff 11mo agoCan someone translate this from marketing puff into something meaningful? All I'm seeing is 'lambdas should map to micro services' 'please use more managed services'
- mlhpdx 11mo agoThe article is basically making the point that deploying bits of runtime code, even something as simple as a single purpose cloud function, is unnecessary and makes work. The examples of using StepFunctions (declarative code) and “direct integrations” are given, the latter being the least effort to maintain, but in reality it also hides declarative code inside (e.g. VTL to change the shape of payloads). The benefit is mainly removing the need to deal with runtimes.
- yencabulator 11mo agoWhat stupid buzzword drivel. Emphasis mine. > [...] you may actually find your Step *Functions* workflow doing all the computation and data manipulation, without a single function, completely and blissfully *functionless*!