boneslabs v2 catalog platform

1 min read

BonesLabs v2 Catalog Platform

the problem

The first BonesLabs storefront — a headless Next.js front end over a WooCommerce backend — did its job, but the catalog ambition outgrew it. Eight hundred thousand products do not fit a plugin-driven commerce platform: search slows, imports choke and every page render drags the database with it.

what we built

A catalog platform designed from scratch for that scale. A Rust API owns the catalog and order logic. A server-rendered .NET front end delivers pages without a client-side waterfall. Meilisearch answers faceted queries in milliseconds across the full catalog, and PostgreSQL remains the system of record. The architecture separates catalog ingestion from serving so a bulk import never degrades the storefront.

what it changed

Catalog size stops being the limiting factor on the business. Search is fast at the full product count, pages render predictably under load, and the engineering team has a typed, tested codebase instead of a plugin stack to reason about.

Have a problem in this neighbourhood?

Tell us about it. A senior engineer reads every message.

let's talk
in plain terms

You have read enough websites promising transformation. We would rather tell you exactly what a forward deployed engineer does, what it costs you in attention, and what you get back — before you decide to talk to us.

the straight talk