3 ms·
Structure your data (both on your data base and in your programs) AS IF you already had billions of records. Do this from the start. It takes no more time tha
by edw519 19y ago
Structure your data (both on your data base and in your programs) AS IF you already had billions of records. Do this from the start. It takes no more time than throwing something together now. It will definitely save you lots of time later.
Also, MINIMIZE the amount of data that travels between client and server, either way, ever. If you don't now, you won't notice the hit in your test environment, but you will notice it later. The problem then may be a lot of restructuring and rewriting.
- ardit33 19y agowhat if my app will never reach a billion records? This seems an overkill. I think when your program, you should program thinking in a this way: What's the max usage groth I can realisticly predict of happening on the next year? If in a year you have the good problem as too many people are siging up for your service, there is many ways to keep that groth and performance happening. Concetrating on having millions of users, when you haven't written a line of code yet, is just an dellusion delaying your progress to even get any users.
- edw519 19y ago"Concetrating on having millions of users" I never said that. I said to structure your data AS IF you had billions of records. Are you going to normalize your data? How much? Are you going to index it? How? How are you going to structure your iterations, branches, and internal data structures? Put any thought into any of it? With rare exceptions, what works well for billions of records also works well for hundreds of records. The converse, unfortunately, is painfully untrue. Think ahead and you won't have to worry about dealing with it.