Web Design and Development en Milan
How we work in Milan
The listing is decided in the database
A catalogue with twenty thousand items is not slow because of the images or the layout: it is slow because the query that renders the listing walks through too many rows and counts them all so it can paginate. It is fixed with indexes designed around the filters people actually use, not with a new template. It is invisible work and it is the work that moves the number.
Counting the results costs more than showing them
The "1,284 products" sitting above the filters usually costs more server time than the twenty-four items on the page. In large catalogues it is solved with approximate counts, with aggregates calculated in advance, or by dropping it altogether if nobody looks at it. Choosing between those three is a business conversation, not an implementation detail.
Laravel and React, with the search engine where it belongs
To filter across dozens of combinable attributes, the relational database on its own falls short and a search engine beside it, kept in sync, earns its place. We build both pieces and decide with your volume in front of us which one takes what, because bolting a search engine onto a small catalogue means complicating your life and paying for two infrastructures.
The code and the product data are yours
Repository, servers and database in your company's name from day one. In a catalogue project this weighs more than in a corporate website: product data is the real asset of the business, and whoever hosts it in their own account is the one who holds the relationship.
Answering your questions
What people ask us about Web Design and Development in Milan.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Web Design and Development: stack, process, use cases and FAQs