4 ms·
people want to go back to monoliths, but don't want to lose the upsides of microservices. once you get a taste of serverless, it's really hard to go back to ove
by turingbike 5y ago
people want to go back to monoliths, but don't want to lose the upsides of microservices. once you get a taste of serverless, it's really hard to go back to overprovisioning. at the same time, distributed state and logic that crosses service boundaries is hard. I don't know what comes next, but what I _want_ to come next is powerful static analysis that works across languages and services, that can "compile down" to serveless services
- tmzt 5y agoMaybe something like ballistacompute.org? I can see a language agnostic distributed solution powered by async/await with type definitions constantly automatically compiled to the target language, all wrapped up in an ide with team-level versioning. Native support for event driven, streaming, and batch data with little ceremony. Throw in distributed ipfs-like storage with persistant references and eager caching and a strongly-typed graph database for good measure.