CloudEvents, interoperability & feature of the internet tech

Lukas Liesis
1 min readNov 26, 2021

I wish after this decade many APIs on the internet would return responses followed by CloudEvent specification. Doesn’t matter https, wss or any other protocol of the time. I find it so much easier to work with tech which is based on events patterns throughout the stack. So much easier to debug, test, fix & automate. Connect things as you wish in a quick and manageable way. Use cloud-state machines to orchestrate the flows like AWS State Machine (part of AWS Step Functions) or “time-travel” (popularized by redux a lot).

Like when *this tech thing* all started people worried about disk space, then cpu & ram. And it made total sense, it costed a lot lot. But now these resources are so cheap and available, question is what is next abstraction layer to worry about. Interoperability & standardization seems like should be at the core. Defining quality of building blocks for better & more complex apps. It has direct influence on business requirements delivery speed & quality.

Services become so complex that standardization how they communicate is critical. Many companies should not build all components from scratch. It’s just waste of resources. Standardization makes it easier to never rebuild same parts again, but better polish them to perfection, reuse & extend. Just like many now sees why running on lambda is such a better approach then tinkering your yet another linux box.

--

--

Lukas Liesis

2 decades exp of building business value through web tech. Has master's degree in Physics. Built startups with ex-Googlers. Was world’s top 3% developer.