TechFlorenceNext Team
Cost-aware MuleSoft on AWS: the bits we wish someone had told us
Running MuleSoft runtime fabric on AWS gets expensive quietly. These are the patterns we wish someone had told us, that bring cost down without sacrificing the latency budget your SLAs depend on.
Right-size before you autoscale
Most overspend is steady-state, not spikes. Profile real traffic, right-size the baseline fabric, and only then tune autoscaling. Chasing peaks while the floor is wrong just makes an expensive floor elastic.
- Match fabric size to real, profiled traffic.
- Separate latency-critical flows from batch work.
- Watch data transfer cost, not just compute.
Read next
View allMore from the FlorenceNext team
General27 Jan 2026FlorenceNext TeamThe engineering practices that survive a fast-growing consultancy
A short list of rituals that scale, and the ones we deliberately stopped doing as the team passed 30 people.
Tech13 Jan 2026FlorenceNext TeamFrom SOAP to GraphQL: migration tips from real client projects
Practical notes on schema design, auth, caching, and how to move clients across without a hard cutover.
- Tech10 Jun 2026FlorenceNext Team
MuleSoft 4 migration: a pragmatic field guide
What we learned moving a 200-flow estate from Mule 3 to 4 without freezing the business for a quarter.