Great video on high level overviews of scaling your db through replication vs sharding or using a combination. Short, helpful, and easy to understand. Thanks!
Oh, ok. I found most of them but what I'm struggling now is how to piece the puzzle. I have them but i don't know in which order most of them are lol If you got any info on how they are ordered, I'll appreciate if you sahre it.
The answers I thought * (O) get a faster machine -> Vertical scaling. We can improve the read "speed" by buying a bigger machine. * (X) replicate the database -> Horizontal scaling. However, we cannot improve the "speed" because the computing power has not changed. It can only perform more reads at the same time. * (?) store less data -> It also improves the read speed, but is it allowed to store less data? * (O) press the turbo button -> If the turbo means the turboboost of the intel chip processor, this can be an answer too.
But isn’t this something the hosting company will take care of for you... when it come to dealing with database servers? I’m looking for actual code examples with best practice structure. Using programs like PHP & MySQL to store and pull data from multiple tables in a database. Using either a class based structure or a OOP structure witch is very similar to class based structure or a procedural based structure witch uses function as. It’s structure. This type of high level database scalable code example is what I’m looking for... do you have anything like this?
In theory this is all good? Pretty basic. would be good to cover how this is all works? what are links mean here? and how that happens. A DB can end with up 50 -100 tables at min. From web app when i fire a crud operation where the distinction happens which server it should go (slave vs master). Similarly when you have shards, how does that translate. On table y i am querying a select query with where clause or group by? In this how this link is determined. Who does that job?
One way to do this with relational databases might be to store data independently on different systems. For example you could do a lookup for "users" and then you could use that data to look for "telephones" in a separately stored table/db. The disadvantage being that you might need to do many queries for large results. A better solution might be to use NoSQL or Hadoop databases for your data. These systems scale much better for this reason.
hi every one which framework that can use in large scale of developing web systems and which database can use in this web development tips for infrastructure please thanks
