3 ms·
We are closer than that. Services are just aggregation layers for functions. The functions are the things of interest, and the aggregation/abstraction is mean
by CuriouslyC 4y ago
We are closer than that. Services are just aggregation layers for functions. The functions are the things of interest, and the aggregation/abstraction is meaningless from a runtime perspective. By creating a function-first architecture (ala Lambda) using a runtime with a common compilation target (e.g. WASM), you can have a single code-base with hints/IDE navigation while also allowing for polyglot execution.
- dagss 4y agoI think many (including me) would still consider an application written in Lambda functions a monolith. It's how databases are used etc. that matters for service boundaries. There really isn't that much difference between a stateless monolith deployed in k8s, a Lambda function, and a microservices with one function in each service ... it's all just stateless code anyway.