Customer Platform & Integration Services
Multi-layer caching cut third-party API traffic while improving resilience
Architecture and delivery of customer-facing applications and integration services spanning booking, checkout, payments, customer profiles, claims, CMS, analytics and lead management — on AWS serverless with TypeScript.
- Solution Architect
- Oct 2025 – Present
Categories
- Solution Architecture
- Serverless
- Integrations
Technologies
- AWS Lambda
- API Gateway
- DynamoDB
- CloudFront
- Amplify
- React
- Next.js
- TypeScript
- Node.js
- Webflow
- Mindbody
- RepairQ
- Creatio
Context
Outliant builds customer-facing products for clients whose operations run on specialised third-party platforms — booking (Mindbody), repair and claims management (RepairQ), CRM and lead management (Creatio), marketing sites (Webflow). As Solution Architect I own how those platforms come together into coherent web applications and integration services.
What I do
- Design and deliver customer-facing applications and integration services across booking, checkout, payments, customer profiles, claims, CMS, analytics and lead-management workflows.
- Build and guide the implementation of AWS-based serverless services and APIs with TypeScript, Node.js, Lambda, API Gateway and DynamoDB, fronted by CloudFront and Amplify.
- Define API contracts, data flows, error-handling behaviour, caching strategies, deployment requirements and observability expectations together with frontend and backend engineers.
- Review code, troubleshoot production issues, document root causes and coordinate remediation across product, design, QA, delivery and engineering teams.
Outcome
Designed multi-layer caching and asynchronous refresh patterns that materially reduced third-party API traffic while improving application performance and resilience — the integrations stay responsive even when upstream platforms are slow or rate-limited.