Simran

<div class="ql-editor read-mode"><p><span style="background-color: transparent; color: rgb(21, 40, 61);"><img src="/files/DzWdWWA.png" height="52" width="206"></span></p><p><strong style="background-color: transparent; color: rgb(230, 110, 50);">DATABASE ARCHITECTURE</strong></p><p><strong style="background-color: transparent; color: rgb(22, 78, 133);">The Day CREATE EXTENSION Became a Platform Decision</strong></p><p><span style="background-color: transparent; color: rgb(92, 107, 120);">Why useful PostgreSQL capabilities need a catalogue, compatibility evidence and an owner.</span></p><p><em style="background-color: transparent; color: rgb(21, 40, 61);">A developer asked for one extension to solve one problem. The SQL took seconds. The review uncovered an operating-system package, a shared library, a preload change, background workers and an upgrade dependency that would live for years.</em></p><p><strong style="background-color: transparent; color: rgb(230, 110, 50);">Start with one workload | Scale into a complete platform | Open Source Freedom | Enterprise-Grade Operations.</strong></p><p><span style="background-color: transparent; color: rgb(21, 40, 61);">Published | January 2026</span></p><h1><strong style="background-color: transparent; color: rgb(22, 78, 133);">The question behind the obvious answer</strong></h1><p><span style="background-color: transparent; color: rgb(21, 40, 61);">A developer asked for one extension to solve one problem. The SQL took seconds. The review uncovered an operating-system package, a shared library, a preload change, background workers and an upgrade dependency that would live for years.</span></p><p><span style="background-color: transparent; color: rgb(21, 40, 61);">Extensions are part of PostgreSQL’s strength, but unmanaged extensions turn database freedom into hidden platform coupling.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);"><em>An Extension Is Code Inside The Database Trust Boundary.</em></strong></td></tr></tbody></table><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">The turning point</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The platform introduced an approved catalogue that connected business use, PostgreSQL version, package provenance, runtime requirements, licensing and rollback constraints.</span></p><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The team used OSS Manager to make approved PostgreSQL extension lifecycle reviewable and repeatable. The engine still owned its native behaviour; the control plane made intent, prerequisites, execution and evidence visible to the people responsible for the service.</span></p><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">What had to become explicit</strong></h2><ul><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">The service boundary: An approved extension catalog maps PostgreSQL and operating-system versions to signed packages, preload requirements, database enablement, rollback constraints, and test evidence.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">The operational controls: allow-list, package signature and SBOM, binary compatibility, preload change review, dependency graph, database scope, backup, rollback, and license review.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">The capacity conversation: extension workload, memory and background workers, index growth, maintenance cost, query patterns, package footprint, and upgrade duration.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">The human boundary: who may observe, who may approve, who may execute, and who decides whether the application is ready.<br></span></li></ul><h1><strong style="background-color: transparent; color: rgb(22, 78, 133);">The architecture that changed the conversation</strong></h1><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The diagram is deliberately centred on the decision the team had to make. It is not a product inventory. It shows where authority sits, what crosses the boundary, and where a failed assumption must stop the workflow.</span></p><p style="text-align: center;"><span style="background-color: transparent; color: rgb(21, 40, 61);"><img src="/files/xqqH8uY.png" height="454" width="888"></span><strong style="background-color: transparent; color: rgb(22, 78, 133);"><br></strong></p><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">The practical design choices</strong></h2><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Gate</strong></td><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Question</strong></td><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Evidence</strong></td></tr><tr><td data-row="2"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Compatibility</strong></td><td data-row="2"><span style="background-color: transparent; color: rgb(21, 40, 61);">Will it survive the next major version?</span></td><td data-row="2"><span style="background-color: transparent; color: rgb(21, 40, 61);">Version matrix</span></td></tr><tr><td data-row="3"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Runtime</strong></td><td data-row="3"><span style="background-color: transparent; color: rgb(21, 40, 61);">Does it need preload or workers?</span></td><td data-row="3"><span style="background-color: transparent; color: rgb(21, 40, 61);">Restart and resource plan</span></td></tr><tr><td data-row="4"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Recovery</strong></td><td data-row="4"><span style="background-color: transparent; color: rgb(21, 40, 61);">Can backups restore the objects?</span></td><td data-row="4"><span style="background-color: transparent; color: rgb(21, 40, 61);">Restore test</span></td></tr><tr><td data-row="5"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Security</strong></td><td data-row="5"><span style="background-color: transparent; color: rgb(21, 40, 61);">What code enters the trust boundary?</span></td><td data-row="5"><span style="background-color: transparent; color: rgb(21, 40, 61);">Package provenance and privilege review</span></td></tr><tr><td data-row="6"><strong style="background-color: transparent; color: rgb(21, 40, 61);">Licensing</strong></td><td data-row="6"><span style="background-color: transparent; color: rgb(21, 40, 61);">Can it be redistributed and supported?</span></td><td data-row="6"><span style="background-color: transparent; color: rgb(21, 40, 61);">Approved licence and ownership record</span></td></tr></tbody></table><p><span style="background-color: transparent; color: rgb(21, 40, 61);">These choices are intentionally small enough to review and test. They keep the architecture tied to operating behaviour instead of allowing a visually impressive diagram to hide unclear ownership.</span></p><h1><strong style="background-color: transparent; color: rgb(22, 78, 133);">What OSS Manager changed - and what it did not</strong></h1><p><span style="background-color: transparent; color: rgb(21, 40, 61);">OSS Manager brought discovery, planning, guarded execution and normalised status into one path for PostgreSQL. It did not replace the engine's correctness model or the application's responsibility for data semantics.</span></p><ul><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">Before change, validate versions, hosts, identities, artifacts, topology and the recovery boundary without mutating the service.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">During change, persist progress, expose stop conditions and prevent a partial result from being mistaken for success.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">After change, observe extension version; load success; background worker health; error log; query latency; resource use; package drift; unsupported dependency and run representative application journeys, not only process checks.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="background-color: transparent; color: rgb(21, 40, 61);">For recovery, protect the last known-good authority and require an explicit decision before promotion, rollback or destructive cleanup.</span></li></ul><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">The failure modes worth rehearsing</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The test plan should make room for missing shared library, incompatible ABI, preload error, dependency conflict, extension update failure, catalog drift, unsupported downgrade, and license exception. The purpose is not to produce a longer checklist. It is to learn whether operators can recognise the failure and choose the safe next action while the evidence is incomplete.</span></p><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">A human operating model</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">L1 operators need a plain-language answer to what is healthy, what is delayed and whether a change is in progress. Platform engineers need topology and evidence. Application owners need to know what users will experience. A useful platform connects those views without giving every person the same privileges.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);"><em>The catalogue did not reduce innovation. It shortened the path from a good idea to a supportable production capability.</em></strong></td></tr></tbody></table><h1><strong style="background-color: transparent; color: rgb(22, 78, 133);">Where this pattern earns its place</strong></h1><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">Media and OTT</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">This pattern is relevant where teams need regional continuity, burst traffic, low-latency serving and predictable recovery. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">Retail</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">This pattern is relevant where teams need campaign peaks, catalogue freshness, transaction continuity and rapid rollback. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h2><strong style="background-color: transparent; color: rgb(22, 78, 133);">Telecom</strong></h2><p><span style="background-color: transparent; color: rgb(21, 40, 61);">This pattern is relevant where teams need high event volume, distributed operations, identity boundaries and service assurance. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h1><strong style="background-color: transparent; color: rgb(22, 78, 133);">The lesson we would carry into the next project</strong></h1><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The catalogue did not reduce innovation. It shortened the path from a good idea to a supportable production capability.</span></p><p><span style="background-color: transparent; color: rgb(21, 40, 61);">The strongest open-source platforms are not the ones with the most automation. They are the ones where automation makes ownership, risk and recovery easier for people to understand.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="background-color: transparent; color: rgb(21, 40, 61);"><em>Start with one workload. Prove the operating model. Then scale it into a complete platform.</em></strong></td></tr></tbody></table><p><br></p></div>

Explore PostgreSQL extension security, compatibility, package provenance and lifecycle governance with clear ownership and reliable recovery

PostgreSQL Extension Management | OSS Manager

writing-the-day-create-extension-became-a-platform-decision

Writing  The Day CREATE EXTENSION Became a Platform Decision

<div class="ql-editor read-mode"><p><strong style="color: rgb(230, 110, 50); background-color: transparent;">EVENT STREAMING</strong></p><h1><strong style="color: rgb(22, 78, 133); background-color: transparent;">A Day in the Life of a Kafka Platform Team After the First Hundred Topics</strong></h1><p><span style="color: rgb(92, 107, 120); background-color: transparent;">Why partition health, controller quorum and application contracts must be operated as one system.</span></p><p><em style="color: rgb(21, 40, 61); background-color: transparent;">At ten topics, the platform team knew every producer. At one hundred, a routine broker restart could expose a weak replication factor, a noisy consumer, a full disk and a certificate nearing expiry in the same maintenance window.</em></p><p><strong style="color: rgb(230, 110, 50); background-color: transparent;">Start with one workload | Scale into a complete platform | Open Source Freedom | Enterprise-Grade Operations.</strong></p><p><span style="color: rgb(21, 40, 61); background-color: transparent;">Published | May 2026</span></p><h2><strong style="color: rgb(22, 78, 133); background-color: transparent;">Growth changes the questions</strong></h2><p><span style="color: rgb(21, 40, 61); background-color: transparent;">At ten topics, the platform team knew every producer. At one hundred, a routine broker restart could expose a weak replication factor, a noisy consumer, a full disk and a certificate nearing expiry in the same maintenance window.</span></p><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The cluster could be technically available while the business stream was not. A green broker count did not answer whether partitions were online, consumers were catching up, or a rolling operation was still safe.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="color: rgb(21, 40, 61); background-color: transparent;"><em>Kafka Incidents Rarely Begin With Kafka Alone.</em></strong></td></tr></tbody></table><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">The turning point</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The operating model moved from host automation to workload-aware gates: quorum first, partition safety next, consumer impact visible, and every rolling step able to stop.</span></p><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The team used OSS Manager to make governed Kafka KRaft platform operations reviewable and repeatable. The engine still owned its native behaviour; the control plane made intent, prerequisites, execution and evidence visible to the people responsible for the service.</span></p><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">What had to become explicit</strong></h3><ul><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">The service boundary: A KRaft controller quorum and broker fleet are declared with rack awareness, TLS, ACLs, monitoring, storage policy, and controlled rolling operations.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">The operational controls: quorum sizing, rack placement, replication factor, minimum in-sync replicas, listener validation, rolling safety, ACL separation, and partition health.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">The capacity conversation: ingress and egress throughput, retention, partitions, replication factor, message size, consumer fan-out, recovery bandwidth, and disk headroom.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">The human boundary: who may observe, who may approve, who may execute, and who decides whether the application is ready.<br></span></li></ul><h2><strong style="color: rgb(22, 78, 133); background-color: transparent;">The architecture that changed the conversation</strong></h2><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The diagram is deliberately centred on the decision the team had to make. It is not a product inventory. It shows where authority sits, what crosses the boundary, and where a failed assumption must stop the workflow.</span></p><p style="text-align: center;"><span style="color: rgb(21, 40, 61); background-color: transparent;"><img src="https://operate.hybrowlabs.com/files/ZMeQS1S.png" height="454" width="888"></span><strong style="color: rgb(22, 78, 133); background-color: transparent;"><br></strong></p><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">The practical design choices</strong></h3><ul><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><strong style="color: rgb(21, 40, 61); background-color: transparent;">Under-replicated partitions. </strong><span style="color: rgb(21, 40, 61); background-color: transparent;">What it reveals: Reduced failure margin. Decision: Hold rolling change.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><strong style="color: rgb(21, 40, 61); background-color: transparent;">Consumer lag. </strong><span style="color: rgb(21, 40, 61); background-color: transparent;">What it reveals: Business processing delay. Decision: Protect recovery bandwidth.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><strong style="color: rgb(21, 40, 61); background-color: transparent;">Disk watermark. </strong><span style="color: rgb(21, 40, 61); background-color: transparent;">What it reveals: Retention and restart risk. Decision: Add capacity or reduce pressure.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><strong style="color: rgb(21, 40, 61); background-color: transparent;">Controller quorum. </strong><span style="color: rgb(21, 40, 61); background-color: transparent;">What it reveals: Metadata authority is at risk. Decision: Restore majority before lifecycle work.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><strong style="color: rgb(21, 40, 61); background-color: transparent;">Certificate horizon. </strong><span style="color: rgb(21, 40, 61); background-color: transparent;">What it reveals: Clients may fail together. Decision: Rotate and validate before expiry.</span></li></ul><p><span style="color: rgb(21, 40, 61); background-color: transparent;">These choices are intentionally small enough to review and test. They keep the architecture tied to operating behaviour instead of allowing a visually impressive diagram to hide unclear ownership.</span></p><h2><strong style="color: rgb(22, 78, 133); background-color: transparent;">What OSS Manager changed - and what it did not</strong></h2><p><span style="color: rgb(21, 40, 61); background-color: transparent;">OSS Manager brought discovery, planning, guarded execution and normalised status into one path for Apache Kafka. It did not replace the engine's correctness model or the application's responsibility for data semantics.</span></p><ul><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">Before change, validate versions, hosts, identities, artifacts, topology and the recovery boundary without mutating the service.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">During change, persist progress, expose stop conditions and prevent a partial result from being mistaken for success.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">After change, observe controller quorum; broker health; under-replicated partitions; offline partitions; ISR changes; request latency; disk; consumer lag; rebalance rate and run representative application journeys, not only process checks.</span></li><li data-list="bullet"><span class="ql-ui" contenteditable="false"></span><span style="color: rgb(21, 40, 61); background-color: transparent;">For recovery, protect the last known-good authority and require an explicit decision before promotion, rollback or destructive cleanup.</span></li></ul><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">The failure modes worth rehearsing</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The test plan should make room for controller loss, broker loss, ISR shrink, offline partition, disk watermark, certificate expiry, consumer rebalance storm, and unsafe rolling restart. The purpose is not to produce a longer checklist. It is to learn whether operators can recognise the failure and choose the safe next action while the evidence is incomplete.</span></p><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">A human operating model</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">L1 operators need a plain-language answer to what is healthy, what is delayed and whether a change is in progress. Platform engineers need topology and evidence. Application owners need to know what users will experience. A useful platform connects those views without giving every person the same privileges.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="color: rgb(21, 40, 61); background-color: transparent;"><em>Kafka became easier to run when the team stopped asking 'are the brokers up?' and started asking 'is the event service safe to change?'.</em></strong></td></tr></tbody></table><h2><strong style="color: rgb(22, 78, 133); background-color: transparent;">Where this pattern earns its place</strong></h2><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">BFSI</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">This pattern is relevant where teams need controlled change, explicit authority, auditable recovery and customer-journey validation. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">Media and OTT</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">This pattern is relevant where teams need regional continuity, burst traffic, low-latency serving and predictable recovery. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h3><strong style="color: rgb(22, 78, 133); background-color: transparent;">Retail</strong></h3><p><span style="color: rgb(21, 40, 61); background-color: transparent;">This pattern is relevant where teams need campaign peaks, catalogue freshness, transaction continuity and rapid rollback. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.</span></p><h2><strong style="color: rgb(22, 78, 133); background-color: transparent;">The lesson we would carry into the next project</strong></h2><p><span style="color: rgb(21, 40, 61); background-color: transparent;">Kafka became easier to run when the team stopped asking 'are the brokers up?' and started asking 'is the event service safe to change?'.</span></p><p><span style="color: rgb(21, 40, 61); background-color: transparent;">The strongest open-source platforms are not the ones with the most automation. They are the ones where automation makes ownership, risk and recovery easier for people to understand.</span></p><table class="table table-bordered"><tbody><tr><td data-row="1"><strong style="color: rgb(21, 40, 61); background-color: transparent;"><em>Start with one workload. Prove the operating model. Then scale it into a complete platform.</em></strong></td></tr></tbody></table><p><br></p></div>

Explore Kafka platform operations, partition health, controller quorum and safe changes with clear ownership and reliable recovery.