<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Native Software Engineering · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2307.01045/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2307.01045/feed.xml" rel="self" type="application/rss+xml" /><item><title>Cloud Native Software Engineering — mentioned by bob1029</title><link>https://news.ycombinator.com/item?id=38569075</link><guid isPermaLink="false">urn:hackerpapers:mention:2307.01045:38569075</guid><pubDate>Fri, 08 Dec 2023 13:57:30 GMT</pubDate><description>&lt;p&gt;&amp;gt; Are there any under-the-radar shifts that you think people are currently unaware of? Cloud-native consolidation of tech stacks &amp;amp; teams. When I say &amp;quot;cloud-native&amp;quot;, I am very specifically referring to the definition outlined in a recent paper [0]. Right now, there is a miasma of uncertainty when you walk into a room and say &amp;quot;cloud native&amp;quot;. Most people right now think you intend to spin up a K8s cluster or something to that effect. A circus of complexity for its own sake, most likely. A few of us are now using the bare-ass, cloud-native FaaS runners as prescribed above and seeing how this can…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2307.01045/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Cloud Native Software Engineering — mentioned by bob1029</title><link>https://news.ycombinator.com/item?id=38151724</link><guid isPermaLink="false">urn:hackerpapers:mention:2307.01045:38151724</guid><pubDate>Sun, 05 Nov 2023 15:05:04 GMT</pubDate><description>&lt;p&gt;&amp;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. So, Microsoft Orleans, Akka, et. al.? This feels like rediscovery of virtual actor models to me - aka not the right answer for most business applications. The end game is proper cloud-native, which means stop thinking about 100% of this bullshit. Alternatively, you need to take full ownership and do it all with single machine monoliths on-prem.…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2307.01045/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Cloud Native Software Engineering — HN submission</title><link>https://news.ycombinator.com/item?id=36595673</link><guid isPermaLink="false">urn:hackerpapers:submission:2307.01045:36595673</guid><pubDate>Wed, 05 Jul 2023 05:01:06 GMT</pubDate><description>&lt;p&gt;Cloud Native Software Engineering&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;43 points; 30 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2307.01045/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
