Stabilizing and Scaling Spobik
Turning a slow e-commerce site into a fast, secure revenue-generating platform
Key Results:
- 6x faster load time (600 ms → 38 ms)
- Updates for 500,000+ items in ~10 min
- Largest Contentful Paint: 0.24 seconds
Search stays as it was in 2019 because the module sits three layers deep in the monolith. Every vendor demo promises MACH, and every quote assumes an 18-month rewrite with a hiring freeze on new features. Forbytes moves you to composable commerce by cutting one domain at a time — storefront first, then catalog, then checkout — while the current platform keeps processing orders.
| Composable Commerce Benefit | Business Impact |
|---|---|
| Storefront releases independent of backend cycles | Campaigns launch on marketing's schedule, not on the release train |
| Each capability sits under its own contract | You renegotiate or replace one vendor without touching the rest |
| Traffic-heavy services scale on their own | Peak load costs less because you stop scaling the whole platform |
| Market-specific logic lives in its own service | New country launches ship in weeks without core code changes |
| Failure and regression scope limited to one domain | A bad release affects one capability instead of the whole store |
| Migration runs one domain per release | The roadmap keeps moving while the architecture changes underneath |
Domain MappingWe split the platform into catalog, cart, orders, and promotions.
|
#2
|
Pilot ServiceOne service runs behind a proxy while the monolith stays live, so traffic can shift gradually.
|
#4
|
Orchestration LayersHolding vendor contracts, events, and data rules in one API layer.
|
#6
|
|
#1
|
Cut Sequence DefinitionWe select the first component to detach and define the seams.
|
#3
|
Storefront DecouplingThe storefront moves to its own release cycle and CDN edge.
|
#5
|
Domain RolloutRepeating the migration until the core holds only orders.
|
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
This depends on a variety of factors, including your business goals, software requirements, scalability requirements, number of software components within the system, etc. The approximate lower bound of the work volume is around 1800-2500 hours. This includes core integration of a headless front-end, ecommerce site, and PIM. The more customizations and composable apps are needed, the more time it will take to complete the project.
That is the default approach. Most retailers detach the storefront and search first, keep checkout and order management inside the platform, and stop there for a year or more. A partial architecture that ships is worth more than a full MACH stack.
An orchestration layer sits between the storefront and the services. Vendors talk to it through defined contracts, not to each other. It owns retries, idempotency keys, event ordering, and data mapping, so a vendor swap changes one adapter rather than eight call sites. We also cap the vendor count — every added service needs a named owner and a replacement plan.
Each detached service runs behind a proxy alongside the old path, and we compare latency and error rates on live traffic before shifting users. If the new path loses, traffic routes back to the monolith in minutes. We publish p95 numbers per domain at every cutover.
Your team. We build with your engineers in pairs, write runbooks per service, and run the last two cutovers as observers. Where you need ongoing capacity, our engineers stay on the platform team rather than in a separate vendor lane.