For the operations that must not half-complete
AWS consulting for systems that have to finish what they start
TechFabric provides AWS consulting and development: migration onto AWS, serverless and container platforms, Databricks on AWS for the data layer, and durable workflows on Temporal for the operations that span days and several systems. We build on AWS where a system has to reach past the workspace, and we run what we build.
- Who it is for
- Engineering leaders running production on AWS, or moving a workload there
- Bench
- 115+ engineers, averaging 15 years each
AWS gives you every primitive and no opinion about how they fit together. Most of the estates we are called into are not short of services. They are short of a design that says which of them holds the state, what happens when a step fails at three in the morning, and who can explain afterwards what the system did.
What the assessment covers
- Every account, VPC and workload, and who owns each, because the estate usually has more accounts than the org chart has teams
- IAM: what a role can actually reach, and where a service has more than it needs
- Which workloads belong on Lambda, which on containers, and which should stay on an instance and stop being apologised for
- The data layer on S3, Redshift and RDS, and which of it belongs on Databricks on AWS instead
- The long-running processes hidden in queues and cron jobs, which is where the outages come from
- Reserved capacity, savings plans and the licences that change price on the other side of a move
What we build on AWS
- Accounts, network and identity defined as code, so a new environment is a pull request rather than a project
- Migration in reversible waves against an agreed inventory, with the rollback position built before the wave runs
- Serverless and container platforms on Lambda, ECS and EKS, chosen per workload on evidence rather than preference
- Durable workflows on Temporal for the operations that call several systems, wait on a person and must never half-complete
- The data platform on Databricks on AWS, governed by Unity Catalog, where the workload has outgrown a database
- Cost measured against the old estate monthly, so the business case survives contact with the bill
Clients we have done this for
Automotive / Fintech
SWBC
TechFabric rebuilt SWBC's LOSExpress platform for credit unions: the user experience, the design system, and the front-end architecture.
Health & Wellness
Athlinks
Athlinks needed a pipeline to stitch together more than 400 million athlete records across disparate sources. TechFabric built a multi-tiered serverless architecture on Temporal, giving the team granular control, automated retries, and real-time visibility across a complex pipeline.
Warehouse management
Funko
A warehouse management system built to cut operating expense, reduce reliance on manual work, and double throughput efficiency.
FAQ
AWS consulting: common questions
Are you an AWS partner?
We build and run production systems on AWS and are not enrolled in the AWS Partner Network. Our partner standing is with Databricks, Temporal and Microsoft. On AWS the evidence is the published work: Athlinks' durable pipelines on Temporal and AWS, SWBC's platform, and Funko's commerce systems, all named on this site.
Serverless or containers?
Per workload, on evidence. Short, spiky, stateless work belongs on Lambda. Long-running services with steady load usually cost less and behave better on ECS or EKS. Anyone who answers the question before seeing the workload is telling you about their preference rather than your system.
Where does Temporal fit on AWS?
Underneath any operation that spans several systems, takes longer than a request and must not half-complete: an order that ships and refunds, a loan that funds, a pipeline that retries.
Step Functions can express some of that; Temporal keeps the history, survives a worker restart and lets a person approve a step mid-run. We are a Temporal partner and it is where most of our AWS work sits.
Can you migrate us onto AWS from a data centre?
Yes, against an agreed inventory and in reversible waves, which is the discipline on the cloud migration page. The assessment produces the list of what is not coming, signed, before anything moves, because that list is what stops the date moving twice.
The rest of cloud
Cloud migration
Infrastructure and platform leaders with a deadline and a partial inventory
Cloud transformation
CTOs and platform leaders holding a cloud bill that outgrew the business case
Application modernization
Engineering leaders whose release cadence is falling and cannot stop shipping
Azure consulting
Engineering and infrastructure leaders on Microsoft's cloud, or moving onto it