zlacker

[parent] [thread] 3 comments
1. edmund+(OP)[view] [source] 2023-04-27 01:26:57
I remember it differently - we needed replication for "hot" backups. At that time, scalability was a major issue - so anyone (including businesspeople) wanted to have a scalable architecture. MySQL spoke to the practical (default install on cPanel hosts, easy replication) and the aspirational (you're going to blow up and need to scale).

Digg.com also had a really influential technical team - hearing about how they did things set a lot of baseline defaults for a lot of people.

replies(1): >>p_l+m1
2. p_l+m1[view] [source] 2023-04-27 01:39:16
>>edmund+(OP)
maybe you were on the more funded side of history in this. As for me, Digg is way after LAMP got solidly plonked into "what I need for a dynamic website on cheap".

Essentially, start at 2000-2001 and more and more people going into running websites for all kinds of reasons (forums, blogs, webshops, etc. often hosted on low end offerings)

replies(2): >>edmund+0E2 >>int_19+CU2
◧◩
3. edmund+0E2[view] [source] [discussion] 2023-04-27 18:13:17
>>p_l+m1
I didn't enter the workforce until 2004, so yeah missed some of the early early days of PHP/MySQL. I used it for government work, was definitely not well funded haha! But I suspect digg started with MySQL b/c of similar reasons as anyone else, then helped amplify the cycle.
◧◩
4. int_19+CU2[view] [source] [discussion] 2023-04-27 19:27:12
>>p_l+m1
"Cheap" is the key word here, and that usually meant shared hosting, which was like 99% MySQL.
[go to top]