Towards Modern Development of Cloud Applications [pdf]

Reading this I'm thinking "this sounds super similar to serviceweaver". Turns out, it's serviceweaver they're talking about :)

&gt; Distributed object frameworks like CORBA, DCOM, and Java RMI use a <i>programming model similar to ours</i> but suffered from a number of technical and organizational issues [ 58] and don’t fully address C1-C5 either.<p>And the pendulum swings back yet again.

&gt; Underneath the programming model lies a runtime that is responsible for distributing and executing components. The runtime makes all high-level decisions on how to run components. For example, it decides which components to co-locate and replicate.<p>So, Microsoft Orleans, Akka, et. al.?<p>This feels like rediscovery of virtual actor models to me - aka not the right answer for most business applications.<p>The end game is <i>proper</i> cloud-native, which means <i>stop thinking about 100% of this bullshit</i>. Alternatively, you need to take full ownership and do it all with single machine monoliths on-prem. Playing around in the middle is a death sentence (K8s, multiple machines, DIY networking stuff, etc). Your cloud provider should be the one taking psychological damage over this stuff, not your team.<p>There was a paper posted a while back that aptly describes modern development modes relative to the cloud - <a href="https:&#x2F;&#x2F;arxiv.org&#x2F;pdf&#x2F;2307.01045.pdf" rel="nofollow noreferrer">https:&#x2F;&#x2F;arxiv.org&#x2F;pdf&#x2F;2307.01045.pdf</a>. Figure 1 really helps to illustrate the spectrum of thinking. I&#x27;ve been using this aggressively to help various c-suites visualize where we are going. The super weird thing is that they seem WAY more excited about the strategic implications than every developer I know.

Are they trying to reinvent IDL interfaces like in Apache Thrift or Protobuf?