Zero Lock-In Architecture: Provider-Agnostic Service Abstraction and Universal Event Bus for Multi-Product AI Platforms
Fuente:
Zenodo
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Recurso digital |
| Veröffentlicht: |
Zenodo
2026
|
| Schlagworte: | |
| Online-Zugang: | |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| _version_ | 1866901352872935424 |
|---|---|
| author | Sharma, Anil Kumar |
| author_facet | Sharma, Anil Kumar |
| contents | This document is submitted as a defensive publication. No patent rights are asserted. The submission date establishes prior art for each mechanism described. We describe three tightly coupled platform architecture innovations developed in the course of building AnkrStack — a production multi-product AI platform comprising 192 registered services, 121 published packages, and 150+ services that share a common event backbone. The three contributions are: (1) Zero Lock-In Architecture — a full-stack provider abstraction pattern in which every third-party dependency (cloud provider, payment gateway, SMS provider, email provider, LLM provider) is hidden behind a typed abstract interface, enabling any concrete provider to be swapped without changes to application code; (2) @ankr/wire: Universal Event Bus — a single package that abstracts Redis Pub/Sub, MQTT, and in-memory transports behind a unified `emit`/`on` API, ships a registry of 188+ standardized topic names organized by domain using `SERVICE.ENTITY.ACTION` naming convention, provides automatic service health monitoring and reconnection, and unifies event-bus and notification dispatch (SMS, WhatsApp, Telegram, email, push) under a single interface; and (3) @ankr/entity: Base Entity Pattern — an abstract TypeScript class with generic typing that provides full CRUD operations, declarative before/after lifecycle hooks, automatic pub-sub event publication on every mutation, standardized pagination and filtering, and multi-tenant awareness, enabling any domain service to be built in days rather than weeks by extending the base class. Together, these three systems constitute a full-stack answer to vendor lock-in and notification fragmentation at multi-product scale. Each contribution is described with interface contracts, event schemas, architectural diagrams, and implementation evidence from production source code. This document establishes prior art for all mechanisms described. |
| format | Recurso digital |
| id | zenodo_https___doi_org_10_5281_zenodo_19212863 |
| institution | Zenodo |
| language | |
| publishDate | 2026 |
| publisher | Zenodo |
| record_format | zenodo |
| spellingShingle | Zero Lock-In Architecture: Provider-Agnostic Service Abstraction and Universal Event Bus for Multi-Product AI Platforms Sharma, Anil Kumar artificial intelligence ANKR platform domain AI maritime AI This document is submitted as a defensive publication. No patent rights are asserted. The submission date establishes prior art for each mechanism described. We describe three tightly coupled platform architecture innovations developed in the course of building AnkrStack — a production multi-product AI platform comprising 192 registered services, 121 published packages, and 150+ services that share a common event backbone. The three contributions are: (1) Zero Lock-In Architecture — a full-stack provider abstraction pattern in which every third-party dependency (cloud provider, payment gateway, SMS provider, email provider, LLM provider) is hidden behind a typed abstract interface, enabling any concrete provider to be swapped without changes to application code; (2) @ankr/wire: Universal Event Bus — a single package that abstracts Redis Pub/Sub, MQTT, and in-memory transports behind a unified `emit`/`on` API, ships a registry of 188+ standardized topic names organized by domain using `SERVICE.ENTITY.ACTION` naming convention, provides automatic service health monitoring and reconnection, and unifies event-bus and notification dispatch (SMS, WhatsApp, Telegram, email, push) under a single interface; and (3) @ankr/entity: Base Entity Pattern — an abstract TypeScript class with generic typing that provides full CRUD operations, declarative before/after lifecycle hooks, automatic pub-sub event publication on every mutation, standardized pagination and filtering, and multi-tenant awareness, enabling any domain service to be built in days rather than weeks by extending the base class. Together, these three systems constitute a full-stack answer to vendor lock-in and notification fragmentation at multi-product scale. Each contribution is described with interface contracts, event schemas, architectural diagrams, and implementation evidence from production source code. This document establishes prior art for all mechanisms described. |
| title | Zero Lock-In Architecture: Provider-Agnostic Service Abstraction and Universal Event Bus for Multi-Product AI Platforms |
| topic | artificial intelligence ANKR platform domain AI maritime AI |
| url | https://doi.org/10.5281/zenodo.19212863 |