say hello to yoursolutions architect

Have a look

It started on paper.

DeepakA decade ago

I started in graphic design — logos, layout, visual identity. Composition as a system, not a feeling.

Then I discovered UI/UX — and loved it.

DeepakA few years later

Interfaces made the work answerable. A layout can be admired; a flow either survives contact with a person or it does not.

So I started building what I design.

DeepakNot long after

The handoff was the bottleneck. Every translation between design and code lost something, so I removed the translation.

router.post('/orders', handler)async def reconcile(ledger, since):interface Claim { id: string }await queue.publish(event)BEGIN … ON CONFLICT DO NOTHINGretry(backoff='exponential')-- migration 0042: split write path

Then I went underneath.

DeepakLater

An interface is a promise and something has to keep it. Most product pain turns out to be data-model pain wearing a costume.

Now I draw the whole system.

DeepakToday

Cloud and solution architecture. More than a decade in, the useful part is having stood at every layer I am now drawing.

Graphic design, then interfaces, then the code behind them, then the cloud underneath. More than a decade spent moving down the stack without letting go of the top of it.

Prefer email? hello@deepaknatarajan.me

By domain, not by client.

Case study 1
Healthcare
Clinical systems that were never meant to speak to each other
- AWS
- Event-driven
- PostgreSQL
- Compliance
What the work was
Problem
Clinical data spread across systems that were never designed to speak to each other, with compliance requirements that make the easy integration illegal.
Approach
Event-driven boundaries with an explicit audit trail, so every record’s provenance is reconstructable rather than assumed.
Outcome
Teams could ship against a stable contract instead of negotiating with each other’s databases.
Case study 2
E-commerce
Eleven flat months and one vertical one
- AWS
- Edge caching
- Node.js
- Queues
What the work was
Problem
Traffic that is flat for eleven months and vertical for one, against a catalogue and checkout that were written for the flat months.
Approach
Separated read and write paths, pushed the catalogue to the edge, and made the checkout the only thing that has to be strongly consistent.
Outcome
Peak stopped being an event the team dreaded and became a number on a dashboard.
Case study 3
Contact centre
Six tools open to answer one question
- React
- Python
- Integrations
- Real-time
What the work was
Problem
Agents holding six tools open to answer one question, and every new channel making it seven.
Approach
A single composition layer over the existing systems, so channels became inputs to one workflow rather than parallel workflows.
Outcome
Handling time fell because the work stopped being reassembled by a human every call.

Toolkit

Languages: TypeScriptJavaScriptPythonSQL
Web: ReactNext.jsNode.jsTailwind
Mobile: React NativeIonicExpo
Cloud: AWSTerraformDockerCI/CD
Data: PostgreSQLDynamoDBRedisVector search
Design: FigmaDesign systemsPrototyping

say hello to yoursolutions architect

It started on paper.

Then I discovered UI/UX — and loved it.

So I started building what I design.

Then I went underneath.

Now I draw the whole system.

Let’s build something together.

Selected Work

Healthcare

E-commerce

Contact centre

Toolkit