Agreed. Had to get a travel one to go with me on trips…
Agreed. Had to get a travel one to go with me on trips…
Thank you for the answer. I have delt with scaling DBs with tons of data so the alarm bells were ringing. DBs tend to be fine up to a point and then fall over as soon as the isn’t enough ram to cache the data and mask issues of the DB architecture. With the exponential growth of both users and content to cache, my gut tells me this will become a problem quickly unless some excellent coding is done on the back end to truncate remote instance data quickly.
Sadly I am better at breaking systems in wonderful ways than building systems for use, so I can’t be too helpful other than to voice concerns about issues I have ran into before.
A quick question related to the DB, is the data broken into many smaller tables or is most data in one or two tables? If it is all in one, we may run into performance issues as soon as the DB becomes to large as queries run against whole tables unless promised really well.
As an offensive security worker… I can’t help but read people listing out their attack surface 😂
OMG, posts load instantly now, used to take 3 to 15 seconds. I’m in US East Coast for reference.