- Published on
The reconciliation engine behind Neo for Business went through three architectural lives. The real adversary was never throughput. It was time.
Architecture
All Posts
- fintech (5)
- terraform (4)
- distributed-systems (3)
architecture (3)
- career (3)
- aws (3)
- iac (3)
- kafka (2)
- engineering-management (2)
- leadership (2)
- kotlin (2)
- micronaut (2)
- eks (2)
- devops (2)
- platform-engineering (2)
- postgres (2)
- devsecops (2)
- python (1)
- cron (1)
- workplace-relationships (1)
- professional-success (1)
- communication (1)
- startups (1)
- linkedin (1)
- ethics (1)
- reconciliation (1)
- streaming (1)
- laravel (1)
- first-90-days (1)
- gst (1)
- tax-engine (1)
- caching (1)
- rules-engine (1)
- sustainability (1)
- green-engineering (1)
- cloud-computing (1)
- energy-efficiency (1)
- feedback (1)
- cost-optimization (1)
- api-design (1)
- payments (1)
- cdk (1)
- pulumi (1)
- java (1)
- spring-boot (1)
- microservices (1)
- kubernetes (1)
- cicd (1)
- gitops (1)
- github-actions (1)
- argocd (1)
- helm (1)
- security (1)
- vault (1)
- oidc (1)
- motorcyling (1)
- roadtrip (1)
- adventure (1)
- infrastructure (1)
- cloud (1)
- hashicorp (1)
- event-driven (1)
- motorcycling (1)
- triumph (1)
- speed-twin-900 (1)
- bikes (1)
- personal (1)
- hiring (1)
- engineering-leadership (1)
- interviewing (1)
- Published on
The tax engine was the most unforgiving service in Cogoport's finance platform. A wrong rate means a non-compliant invoice. Here's how we built it to be fast, always available, and correct across exports, SEZ supplies, and reverse charge.- Published on
In December 2022 we had six months to build Cogoport's entire business finance platform from scratch. The language and framework choices were the first decisions we made, and they stayed with us every day.