Scalability

Scalability is what decides whether your system still feels fast when the number of people using it grows. Five staff members log in at nine in the morning and everything opens instantly. Add a hundred and the same screen takes twenty seconds. Nothing broke. The work simply got bigger than the machine underneath it.

The causes are usually dull and specific. The most common one is a report that reads the live data while everyone else is trying to use it. A manager opens last month's sales at 8 a.m., the database locks up while it counts, and every cashier in every branch waits. Another is images. A photo straight from a phone can be six megabytes; put forty of them on one page and the page is a quarter of a gigabyte before a single word appears. The third is the server itself, often one small shared box that was fine for the first year.

None of this is a mystery to solve after the fact. It is a set of choices made at the beginning. Copy the heavy reports onto a second copy of the data, so a manager's curiosity cannot slow down the counter. Resize photos on the way in, once, instead of on the way out, every time. Put a number on how many people will use the system in year three, not year one, and size the hosting to that.

Fixing it later costs far more than allowing for it at the start, and the reason is not the hosting bill. It is that the shape of the data has to change, and every screen that touched it has to be rewritten and tested again. Work that would have taken two days in the first month can take six weeks in the second year. Linkysoft asks for the year-three number before writing any code for a web application project, because that single answer changes the design.

Ask a supplier one question before you sign. How many people can this handle at once, and what does the next step up cost. A clear answer means someone has thought about it. Our own Hostrena hosting exists partly so the answer is a number, not a shrug, and Linkysoft would rather give you that number early.