<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TEN-The executive narrative</title>
    <description>The latest articles on DEV Community by TEN-The executive narrative (@ten).</description>
    <link>https://dev.to/ten</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4088344%2F33464398-cd8a-4fc4-8df7-07c75d5fe9d8.png</url>
      <title>DEV Community: TEN-The executive narrative</title>
      <link>https://dev.to/ten</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ten"/>
    <language>en</language>
    <item>
      <title>Nubank: Scaling a Core Banking Engine on Clojure and Microservices</title>
      <dc:creator>TEN-The executive narrative</dc:creator>
      <pubDate>Thu, 27 Aug 2026 13:24:27 +0000</pubDate>
      <link>https://dev.to/ten/nubank-scaling-a-core-banking-engine-on-clojure-and-microservices-3ijf</link>
      <guid>https://dev.to/ten/nubank-scaling-a-core-banking-engine-on-clojure-and-microservices-3ijf</guid>
      <description>&lt;p&gt;How do you build a real-time ledger that serves 100M+ active users with sub-second latency and zero balance discrepancies?&lt;/p&gt;

&lt;p&gt;Nubank dismantled traditional branch banking by engineering a cloud-native, event-driven banking engine from the ground up. Standardizing entirely on Clojure and immutable data structures, their engineering teams run thousands of microservices handling high-concurrency financial state transitions with minimal overhead.&lt;/p&gt;

&lt;p&gt;The Tech Moat: High-throughput functional microservices architecture driving serving costs down to sub-dollar levels per user.&lt;/p&gt;

&lt;p&gt;Architectural Trade-off: Rejecting legacy off-the-shelf core banking mainframes to engineer a proprietary transactional ledger in-house.&lt;/p&gt;

&lt;p&gt;System Design Takeaway: Functional immutability is the ultimate foundation for systems where state corruption and transaction failure are not options.&lt;/p&gt;

&lt;p&gt;👉 Read the full 3-minute technical deep dive: theexecutivenarrative.com&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>enterprisesoftware</category>
      <category>database</category>
      <category>automation</category>
    </item>
    <item>
      <title>Zoho: Why They Own the Bare Metal and Build Their Own Frameworks</title>
      <dc:creator>TEN-The executive narrative</dc:creator>
      <pubDate>Thu, 27 Aug 2026 13:22:22 +0000</pubDate>
      <link>https://dev.to/ten/zoho-why-they-own-the-bare-metal-and-build-their-own-frameworks-3289</link>
      <guid>https://dev.to/ten/zoho-why-they-own-the-bare-metal-and-build-their-own-frameworks-3289</guid>
      <description>&lt;p&gt;While modern SaaS startups spend millions running on AWS and GCP, Zoho built a profitable suite of 55+ applications by owning every layer of the technology stack.  Zoho operates its own private data centers, proprietary application frameworks, and database orchestration engines. By treating cloud infrastructure and software tooling as in-house R&amp;amp;D assets rather than vendor dependencies, Zoho decoupled its scaling costs from public cloud pricing models.  The Tech Moat: Full vertical integration spanning bare-metal servers, custom UI/backend frameworks, and a shared relational schema across 55+ native apps.  Architectural Trade-off: Sacrificing rapid off-the-shelf third-party integrations to build a unified codebase from scratch over decades.  System Design Takeaway: True margin defensibility at enterprise scale comes from infrastructure autonomy and deep R&amp;amp;D discipline.&lt;br&gt;&lt;br&gt;
👉 Read the full 3-minute technical deep dive: theexecutivenarrative.com&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>saas</category>
      <category>webdev</category>
      <category>backend</category>
    </item>
    <item>
      <title>Datadog: The Architecture Behind the Observability Giant</title>
      <dc:creator>TEN-The executive narrative</dc:creator>
      <pubDate>Thu, 27 Aug 2026 13:19:15 +0000</pubDate>
      <link>https://dev.to/ten/datadog-the-architecture-behind-the-observability-giant-451c</link>
      <guid>https://dev.to/ten/datadog-the-architecture-behind-the-observability-giant-451c</guid>
      <description>&lt;p&gt;Every on-call engineer knows the nightmare of a 3 AM cascading failure across microservices. Datadog turned that distributed systems pain into an enterprise observability empire.&lt;/p&gt;

&lt;p&gt;Instead of building isolated monitoring point solutions, Datadog designed a lightweight, universal root agent running directly at the host and container layer. By ingesting metrics, structured logs, and distributed APM traces into a single-pane unified data layer, it eliminated context-switching across engineering teams during critical outages.&lt;/p&gt;

&lt;p&gt;The Tech Moat: Root-level kernel and container agent infrastructure that makes rip-and-replace an unacceptable operational downtime risk.&lt;/p&gt;

&lt;p&gt;Architectural Trade-off: Standardizing on a single telemetry data model rather than stitching together disjointed third-party APM acquisitions.&lt;/p&gt;

&lt;p&gt;System Design Takeaway: The highest-retention enterprise software is embedded at the kernel/infrastructure layer, where replacement risk vastly outweighs tooling cost.&lt;/p&gt;

&lt;p&gt;👉 Read the full 3-minute technical deep dive: theexecutivenarrative.com&lt;/p&gt;

</description>
      <category>devops</category>
      <category>cloud</category>
      <category>architecture</category>
      <category>systemdesign</category>
    </item>
  </channel>
</rss>
