Your Architecture Might Be the Bottleneck

How to Reach 102,000 RPS with Go and Stop Being Afraid of High Load

You can congratulate me — I finally pushed the project into production. 🙂

The project is based on the architectures I published earlier, using my makoDB and silentJSON projects.

For those who were skeptical about whether this architecture actually works in a real-world application, you can take a look at:

https://wszyst.pl

Play around with the filters, search, pagination, and loading speed.

But the most important part is this:

This is a live production project with real data.

It's not a benchmark with synthetic records, not a toy demo, and not a static showcase.

What's interesting under the hood?

There is quite a lot going on:

• Data is prepared during the import process rather than being heavily processed at query time.
• The system works exclusively with indexes.
• Multiple sections and content types.
• Different access levels.
• Landing pages.
• Company promotion features.
• Branding across 8 regions, with the ability to control exactly which page(s) the branding is displayed on.
• Branding can be enabled or disabled instantly.
• Statistics available by hour, week, and month.
• Statistics broken down by people, bots, and browsers.
• You can exclude your own IP from statistics.
• Price-list parsing for an arbitrary number of companies from a configured list, with pagination.
• Product/company cards can display descriptions provided by partners.
• And quite a lot of other things that aren't immediately visible from the frontend.

The interesting part for me is that all of this is running on the same underlying architecture rather than being a collection of special-case hacks.

And yes, there are still unfinished parts

I'm not pretending everything is polished yet.

The universal attribute parser is not fully finished.

The catalogizer still needs work — mostly because there is simply a huge amount of categories to process.

And some of the visual/UI work is still incomplete for the same reason: the amount of content and functionality is much larger than I initially expected.

So this is very much a working production system, not a "look how perfect my demo is" project.

I'm publishing this partly because some of the architectural ideas I previously wrote about are much easier to evaluate when they're running against real data.

If you're interested in database architecture, index-only approaches, import-time data preparation, or building large catalog/search systems without relying on expensive query-time processing, I'd be interested to hear what you think.

And if you want to stress-test it — please do. 😄