Architecture
Integration patterns, data, events — how to design without unnecessary core replacement.
Accounting Integration Hub (1C / Soliq)
Accounting and tax integration hub is an architectural challenge before it is a software feature. The bank needs to connect accounting and tax integration hub across existing systems without creating another fragile island. The objective…
→How to Build a Fintech Layer Around BSS/OSS
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→API Gateway for a Telecom Ecosystem
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Event-Driven Architecture in Telecom
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Antifraud Architecture for Telco Fintech
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Partner API Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Reporting/Data Mart Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Integration With Billing: How Not to Break the Core
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Super App Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Product Catalog Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Offer Engine Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Loyalty Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Wallet Ledger Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Merchant Payments Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Data Governance Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Security Architecture for Partner Ecosystem
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Privacy-by-Design Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Campaign Automation Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Contact Center Integration Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Dealer Portal Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→B2B Portal Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Settlement & Reconciliation Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Data Clean Room Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→MLOps for Churn, Offer and Fraud Models
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Analytics Sandbox for Business Hypotheses
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Notification Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Dispute & Case Management Architecture
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Observability for Telco Fintech
Practical telecom article: business pain, architecture logic, KPIs, risks and an implementation path with SamaraliSoft.
→Why BSS/OSS should not be replaced — build the growth layer around the core
Replacing billing in a live operator is the most expensive and risky path. An architectural breakdown — where the around-core layer ends, which components are mandatory, and how to decide what really needs to change inside the core.
→Monolith vs microservices
The choice between modular monolith and microservices in a bank is not a question of technology fashion but of team operational maturity, core state, and actual business flow. This article walks through when each approach is justified, which architectural mistakes are typical for Central Asian banks, and how to avoid system fragmentation without business cause.
→API/ESB/Event Bus
The integration layer is the foundation of any digital transformation. Without it, every new application builds integrations from scratch, total cost of ownership grows non-linearly, and changes in one system break five others. This article covers three integration models — API gateway, ESB, event bus — and how to combine them in a mature landscape.
→Customer 360 Architecture
Customer 360 in a bank and at a telecom operator is not a CDP procurement but an architectural layer above the existing stack. This article walks through the layer's components — identity resolution, unified profile, event flows, consents — and the approach to building them around existing core systems without core replacement.
→SSOT Architecture
Single Source of Truth is not a single product but an architectural principle. This article walks through how to build SSOT across key data domains in a bank, an operator, or a government organization, which components are mandatory, which political obstacles are typical, and how to overcome them.
→Data Platform Architecture
Modern data platform is not a choice between DWH and data lake but a layered architecture separating raw data, processed models, BI marts, and AI/ML layer. This article walks through components, typical building mistakes, and the approach to a mature data platform for a bank, operator, or industrial enterprise.
→CDP architecture for a telecom operator: where it lives and who owns it
CDP in telecom is not a marketing product, but a layer between billing, network and channels. Architecture, owners, data contracts, typical failure modes.
→Real-time decisioning architecture: how the operator decides in 200ms
NBA, retention trigger, fraud block — each decision needs a fast profile, policies, models and an audit trail. Architecture of the real-time decisioning layer.
→Event bus for an operator: a shared nerve instead of point-to-point integrations
Every new integration in point-to-point is boilerplate and debt. Event bus makes events a first-class architecture object. Topics, contracts, owners.
→Partner API platform: the operator as an API-first provider
Partners need not a custom connector but a predictable API. Architecture of the platform layer: developer portal, gateway, contracts, monetisation, security.
→Notification fabric: one delivery layer instead of ten
Push, SMS, email, voice, in-app — every team has its own stack. Notification fabric centralises delivery, prioritisation, frequency caps, consent. Without it the customer drowns in noise.
→MLOps for an operator: models in prod, not in Jupyter
Most operators have dozens of models in production with no discipline to refresh, monitor or roll back. MLOps is the operating loop for models.
→Master Data Management for an operator: one source of truth for customer, product, dealer
An operator has five 'right' versions of the customer name. MDM establishes the source of truth for critical reference data and ensures its distribution.
→Data clean room: partner data sharing without transferring personal data
The bank wants joint customer profiling, but transferring personal data is not allowed. Clean room is the architecture where data is processed jointly without cross-disclosure.
→Observability stack for an operator: see the system before the customer complains
Metrics, logs, traces — the three pillars without which the operator flies blind. Observability architecture for a multi-system telecom landscape.
→Consent architecture: consent as a structured object, not a tickbox
Consent is not a 'box ticked' record but a structured claim verified in every use case. Architecture of the consent layer in an operator.
→eKYC architecture: identity verification as a reusable capability
eKYC is needed for more than SIM activation. Identity bridge for the bank, app registration, partner verification. Architecture of a reusable identity capability.
→Architecture around the ABS: modernisation without replacing the core
Replacing ABS — 24-36 months and operational risk. Wrap around it — in 6-12 months. Architectural approach for banks with legacy core.
→CDP architecture for the bank
Customer profile above product silos. Identity resolution for the multi-product banking customer, real-time access for channels.
→Event bus for the bank: nervous system of operations
Transactions, payments, applications, alerts — events flowing across 30-50 systems. Event bus makes them first-class objects.
→Partner API platform for the bank
BaaS, open banking, partner integrations — bank-as-API. Architecture of the platform layer with governance, monetisation, security.
→Real-time decisioning architecture for the bank
Fraud, AML, credit, NBA, retention triggers — all need sub-second decisioning. Architecture of the layer in the bank.
→eKYC architecture for the bank
Document, biometric, liveness, registry checks, risk scoring — reusable identity capability for onboarding and step-up auth.
→MLOps architecture for the bank
Credit, fraud, AML, propensity models — dozens in production. MLOps is the operating loop for lifecycle with regulatory traceability.
→Master Data Management for the bank
Customer master, product master, counterparty master — single source of truth for critical entities. Distribution to downstream systems.
→Observability stack for the bank
Metrics, logs, traces for banking infrastructure. Regulatory requirements + SRE discipline.
→Loan origination architecture
From application to booking. Multi-step workflow with decisioning, document management, covenant capture, regulatory filing.
→Consent architecture for the bank
Consent for data use as a structured object. Especially critical for the bank with regulatory exposure and biometric data.
→Government Event Bus: backbone of inter-agency architecture
Event bus makes inter-agency events first-class objects. Foundation for life-event orchestration, real-time decisions, audit trail.
→Government MDM: citizen master, address master, organisation master
MDM in the state — foundation. Citizen master, address master, organisation master, document catalogue. Distribution to agencies via event bus.
→Government Orchestration Platform
Workflow engine for cross-agency processes. Event-driven, stateful, citizen-visible.
→Government API Platform
Federation of API gateways across agencies. Single developer experience for third-party integrations (banks, fintech, businesses).
→Government eKYC Architecture
National identity verification: document, biometric, registry, signed credentials. Used by citizens, banks, services.
→Government Consent Architecture
Per-purpose, per-attribute consent for citizen data usage. Critical for cross-agency sharing, AI processing, partner verification.
→Government Zero-Trust Security
Zero-trust architecture for state systems. No implicit trust, continuous verification, least privilege.
→Government AI Governance Architecture
Technical architecture for AI oversight in the state: registry, monitoring, explainability, citizen recourse.
→Government Notification Fabric Architecture
Centralised notification layer for all state-to-citizen communications.
→Government Data Platform
Cross-agency data lake / warehouse for analytics, ML training, open data publication.
→Government Real-time Decisioning
Real-time decisions for emergency response, fraud detection, eligibility — with regulator-grade audit trail.
→Government Observability Stack
Metrics, logs, traces for state systems with regulator-grade retention.
→Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours