Cryptocurrency backend services for identity checks, exchange integrations, commissions, and referrals.
My role: Backend developer for financial platform services
Scope: KYC/AML, document validation, Binance integration, PostgreSQL, MongoDB, Neo4j, Redis, Elasticsearch
The problem
The exchange needed secure onboarding, fast data models, identity verification, and integrations with liquidity and blockchain infrastructure.
My contribution
I built NestJS services, document and banking verification workflows, and exchange integrations, using relational, document, cache, and search stores for their respective access patterns.
Engineering decision
Choose storage by the access pattern
Approach
Separate relational, document, graph, cache, and search concerns instead of using a single generic persistence interface for every financial and onboarding workflow.
Alternative and tradeoff
More stores add operational cost and consistency boundaries. Each needs a concrete query or ownership reason; a technology list alone does not justify the complexity.
Reviewing the behavior
Review document access, auditability, data retention, integration failures, and accounting invariants. Implementation of KYC/AML workflows does not itself establish regulatory compliance.
Measurement and scope
Client-owned contribution to verification, exchange integration, and data-model workflows. No claim of legal certification or independent compliance assurance is made.