[{"data":1,"prerenderedAt":315},["ShallowReactive",2],{"service:backend:en":3,"cases:en":111},{"id":4,"title":5,"approach":6,"body":21,"capabilities":39,"description":34,"extension":60,"icon":61,"meta":62,"metrics":63,"navigation":70,"order":35,"path":71,"relatedCases":72,"relatedServices":75,"seo":79,"slug":82,"stackGroups":83,"stem":106,"summary":107,"tagline":108,"value":109,"__hash__":110},"services_en\u002Fen\u002Fservices\u002Fbackend.md","Backend Engineering",[7,11,17],{"title":8,"description":9,"icon":10},"Idempotency","Retries are safe by default.","shield",{"title":12,"description":13,"not hardware":14,"icon":16},"Horizontal scaling","Growth via nodes",[15],null,"gauge",{"title":18,"description":19,"icon":20},"Contract testing","Integrations don't break silently.","graph",{"type":22,"value":23,"toc":33},"minimark",[24,29],[25,26,28],"h2",{"id":27},"how-we-do-it","How we do it",[30,31,32],"p",{},"We design the backend around resilience to load and failure: idempotent operations, event-driven integrations, and observability that makes system behavior predictable.",{"title":34,"searchDepth":35,"depth":35,"links":36},"",3,[37],{"id":27,"depth":38,"text":28},2,[40,44,48,52,56],{"title":41,"description":42,"independent releases":43},"Microservices","Clear boundaries",[15],{"title":45,"description":46,"event bus":15,"idempotency":47},"Event-driven","Queues",[15],{"title":49,"description":50,"versioning":15,"backward compatibility":51},"API-first","Contracts",[15],{"title":53,"description":54,"caching":15,"replicas":55},"Data under load","Sharding",[15],{"title":57,"description":58,"metrics":15,"alerting":15,"SLOs":59},"Observability","Tracing",[15],"md","server",{},[64,67],{"value":65,"label":66},"40k+","RPS",{"value":68,"label":69},"\u003C200ms","median latency",true,"\u002Fen\u002Fservices\u002Fbackend",[73,74],"digital-bank","insurance-claims",[76,77,78],"cloud-devops","integration","data-ai",{"title":80,"description":81},"Backend Engineering — HomeITTech","High-load, event-driven services and APIs — microservices, event-driven, idempotency, observability.","backend",[84,92,100],{"group":85,"items":86},"Languages",[87,88,89,90,91],"Java","Python","PHP","Go","PL\u002FSQL",{"group":93,"items":94},"Databases",[95,96,97,98,99],"PostgreSQL","Oracle","MySQL","MongoDB","Redis",{"group":101,"items":102},"Messaging",[103,104,105],"Kafka","RabbitMQ","JMS","en\u002Fservices\u002Fbackend","High-load, event-driven services and APIs that don't fail under load.","Backends that don't blink.","A backend that sustains tens of thousands of requests per second and stays predictable.","gBH0qYBKNKehsfoD-warctvz7fpncFCekRwc53gptmo",[112,222],{"id":113,"title":114,"architecture":115,"body":147,"challenge":175,"cover":176,"description":34,"extension":60,"featured":70,"glance":178,"headlineMetric":191,"impact":193,"industry":204,"meta":205,"navigation":70,"order":206,"path":207,"quote":208,"related":211,"seo":212,"slug":73,"stack":215,"stem":220,"__hash__":221},"cases_en\u002Fen\u002Fcases\u002Fdigital-bank.md","Digital bank",{"nodes":116,"edges":139},[117,121,125,129,132,136],{"id":118,"label":119,"group":120},"app","Mobile app","client",{"id":122,"label":123,"group":124},"gw","API Gateway","edge",{"id":126,"label":127,"group":128},"payments","Payment service","core",{"id":130,"label":131,"group":128},"ledger","Ledger",{"id":133,"label":134,"group":135},"bus","Event bus","infra",{"id":137,"label":138,"group":128},"antifraud","Anti-fraud",[140,141,142,144,145],{"from":118,"to":122},{"from":122,"to":126},{"from":126,"to":130,"label":143},"idempotent",{"from":126,"to":133},{"from":133,"to":137,"label":146},"real-time",{"type":22,"value":148,"toc":170},[149,153,156,160,163,167],[25,150,152],{"id":151},"the-challenge","The challenge",[30,154,155],{},"The team needed to launch a digital bank from scratch and be ready for multiplied user growth without sacrificing payment reliability.",[25,157,159],{"id":158},"the-architecture","The architecture",[30,161,162],{},"We rebuilt the payment path on an event-driven architecture: idempotent operations, an event bus, and real-time anti-fraud. This let us scale processing horizontally and keep latency stable under load.",[25,164,166],{"id":165},"the-impact","The impact",[30,168,169],{},"In 14 months the bank grew to 2.5M users, peak load grew 8× with no degradation, and releases ship with zero downtime.",{"title":34,"searchDepth":35,"depth":35,"links":171},[172,173,174],{"id":151,"depth":38,"text":152},{"id":158,"depth":38,"text":159},{"id":165,"depth":38,"text":166},"Launch a full digital bank and withstand explosive user growth without degrading the payment path and with zero downtime on releases.",{"variant":20,"accent":177},"signal",[179,182,185,188],{"value":180,"label":181},"2.5M","active users",{"value":183,"label":184},"×8","peak load growth",{"value":186,"label":187},"99.99%","uptime",{"value":189,"label":190},"14 mo","to launch",{"value":180,"label":192},"users in 14 months",[194,197,200],{"value":180,"label":195,"note":196},"users","within 14 months of launch",{"value":183,"label":198,"note":199},"peak load","with no latency degradation",{"value":201,"label":202,"note":203},"0","downtime on releases","gradual rollout","banking",{},1,"\u002Fen\u002Fcases\u002Fdigital-bank",{"text":209,"role":210},"The platform handled growth we didn't expect this fast — and never went down.","Director of Digital Products",[74],{"title":213,"description":214},"Digital bank — HomeITTech case","2.5M users in 14 months, 8× peak load growth with no degradation, zero downtime on releases.",[216,217,218,90,103,95,219],"Swift","Kotlin","Kotlin Multiplatform","Kubernetes","en\u002Fcases\u002Fdigital-bank","mkkg6jlRa4sJnntnMg9lxmHeN7EllyfH4bm7klW2O60",{"id":223,"title":224,"architecture":225,"body":250,"challenge":272,"cover":273,"description":34,"extension":60,"featured":70,"glance":276,"headlineMetric":289,"impact":290,"industry":299,"meta":300,"navigation":70,"order":38,"path":301,"quote":302,"related":305,"seo":306,"slug":74,"stack":309,"stem":313,"__hash__":314},"cases_en\u002Fen\u002Fcases\u002Finsurance-claims.md","Claims platform",{"nodes":226,"edges":243},[227,230,233,237,240],{"id":228,"label":229,"group":120},"portal","Claims portal",{"id":231,"label":232,"group":128},"intake","Intake & validation",{"id":234,"label":235,"group":236},"ocr","AI document processing","ai",{"id":238,"label":239,"group":128},"rules","Rules engine",{"id":241,"label":242,"group":128},"payout","Payouts",[244,245,247,248],{"from":228,"to":231},{"from":231,"to":234,"label":246},"documents",{"from":234,"to":238},{"from":238,"to":241,"label":249},"auto-decision",{"type":22,"value":251,"toc":267},[252,254,257,259,262,264],[25,253,152],{"id":151},[30,255,256],{},"Claims were slowed by manual document handling and fragmented checks. The process had to be faster while keeping accuracy.",[25,258,159],{"id":158},[30,260,261],{},"We built an end-to-end digital flow: AI extracts data from documents, the rules engine runs checks and makes automatic decisions, and complex cases go to a human.",[25,263,166],{"id":165},[30,265,266],{},"Processing time dropped by 40%, 70% of documents are handled without manual entry, and the platform sustains over a million claims a year.",{"title":34,"searchDepth":35,"depth":35,"links":268},[269,270,271],{"id":151,"depth":38,"text":152},{"id":158,"depth":38,"text":159},{"id":165,"depth":38,"text":166},"Cut the claim processing time and remove manual data entry from documents without losing check accuracy.",{"variant":274,"accent":275},"flow","violet",[277,280,283,286],{"value":278,"label":279},"−40%","claim processing time",{"value":281,"label":282},"70%","of documents processed automatically",{"value":284,"label":285},"24\u002F7","digital process",{"value":287,"label":288},"1M+","claims per year",{"value":278,"label":279},[291,294,297],{"value":278,"label":292,"note":293},"processing time","from claim to decision",{"value":281,"label":295,"note":296},"automation","of documents without manual entry",{"value":287,"label":288,"note":298},"on one platform","insurance",{},"\u002Fen\u002Fcases\u002Finsurance-claims",{"text":303,"role":304},"Claims speed became our competitive advantage.","Head of Digital Transformation",[73],{"title":307,"description":308},"Claims platform — HomeITTech case","−40% claim processing time, 70% of documents automated, 24\u002F7 digital claims.",[310,311,88,312,95,219],"TypeScript","Vue","ML pipeline","en\u002Fcases\u002Finsurance-claims","0uIfKi8_JzmtkL1hiAw6uN2oqMReP2Mc7p8pdZoiyUM",1793366507061]