[{"data":1,"prerenderedAt":56},["ShallowReactive",2],{"profile-en":3,"project-motor-liquidacao-tempo-real-en":27},{"brandName":4,"fullName":5,"headline":6,"manifesto":7,"contactIntro":11,"avatar":12,"manifestoImage":13,"social":14},"Danilo Fernando","Danilo Fernando - Senior Software Engineer","Well-built software, reliable integrations, and architecture designed to last.",[8,9,10],"My journey is guided by the belief that code is just a tool to solve complex business problems. With solid experience in the Java and Spring ecosystems, I focus on systems that work AND are easy to maintain and evolve.","Specialised in robust APIs and critical integrations, I believe technical maturity shows up in balanced decisions that weigh innovation against real business needs.","I chase real impact: Clean Code is not aesthetics, it is an economic necessity for long-term product sustainability.","I'm always open to new professional opportunities, technical exchange, or conversations about architecture and software engineering.","\u002Fimages\u002Fprofile\u002Fdanilo.webp","\u002Fimages\u002Fprofile\u002Fdanilo_manifesto.webp",[15,19,23],{"kind":16,"label":17,"href":18},"email","Email","mailto:danilo.bossanova@hotmail.com",{"kind":20,"label":21,"href":22},"linkedin","LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fdanilo-fernando-dev\u002F",{"kind":24,"label":25,"href":26},"github","GitHub","https:\u002F\u002Fgithub.com\u002Fdanilobossanova",{"slug":28,"title":29,"summary":30,"tags":31,"context":35,"solution":36,"result":37,"stack":38,"coverImage":43,"publishedAt":44,"metrics":45,"body":55},"motor-liquidacao-tempo-real","Real-Time Settlement Engine","High-volume financial transaction processing with sub-second latency.",[32,33,34],"Fintech","Scalability","Event-Driven","The existing system could not handle volume peaks, causing queues and reconciliation delays.","Event-driven architecture with Spring Boot, Kafka, and natural-key idempotency.","40% reduction in reconciliation time and 99.9% operational availability under heavy load.",[39,40,41,42],"Java 17","Spring Cloud","Kafka","PostgreSQL","https:\u002F\u002Fpicsum.photos\u002Fseed\u002Ffintech\u002F1200\u002F800","2024-11-03",[46,49,52],{"label":47,"value":48},"Reconciliation","-40%",{"label":50,"value":51},"Availability","99.9%",{"label":53,"value":54},"Throughput","12k tps","## Context\nThe legacy settlement core did not scale horizontally...\n\n## Technical decisions\n- Kafka as the event backbone.\n- Outbox pattern for at-least-once guarantees.\n- Natural-key idempotency on consumers.\n\n## Result\nWithin three months reconciliation time dropped 40% with stable throughput above 12k tps.",1776457051877]