oreillynet.com — This article displays a good information on how Digg.com built on LAMP successfully. It seems PHP has won over Java in Web 2.0. Also a small note on DB change. Which DB is the best for a heavy application like Digg.com? Owen Byrne, any clues?
Apr 11, 2006 View in Crawl 4
mistermossApr 12, 2006
[deleted - wrong place for this!]
rayedApr 12, 2006
But Digg is not exactly good showcase for scalability, it is extremely slow.
lanevoApr 12, 2006
Turck MMCache<a class="user" href="http://turck-mmcache.sourceforge.net/index_old.html">http://turck-mmcache.sourceforge.net/index_old.html</a>
angulionApr 12, 2006
To headzoo:While you are right that PHP can run for extensive times (I wrote a Jabber "client/bot"), this is only true for CLI-PHP. Within Apache web-server context you cannot do this.Where I used to work we had an web-based "application" written in PHP to send email and SMS-text messages to customers etc.. This app would have benefited from being able to spawn a separate thread and execute the sometimes 3 hour long process there. As was now, it had a CLI-PHP script ran from cron every 5-10 min to process new jobs.
Closed AccountApr 12, 2006
APC is free and will most likely be included in PHP6.Edit: Gah, those damned reply links are difficult to find. This was meant as a reply to the post by burnt1ce85 below this one.
cheesyApr 13, 2006
geminitojanus: I'm not so sure about your "fewest number of lines" comment. In most languages I could write an entire program on a single line, but that's besides the point. The point is that these days in many cases code readability is more important the program size and efficiency. As one of my CS professors said, "programmer time is more expensive than processor time". Of course that doesn't mean you should write crappy inefficient programs, it means don't prematurely optimize where you don't need to.altjeringa: he did say "whichever language supports the task"... You couldn't write an OS in Java since it's run on a virtual machine. You wouldn't write a 3D engine in Perl since it's interpreted and thus very slow. When you need super fast speed or low level stuff you use something like C or assembly, otherwise you have a pretty wide range of choices these days.
merlin8000Apr 13, 2006
I like PostgreSQL for the best fit for web2.0 programming. One primary reason:Server-side languagesYou can embed PHP, Python, Perl, and really any procedural language into your select statement by building a function written in that language. If you can do that with any other (free) SQL server I haven't seen how, so it's at least more apparent in PostgreSQL
Closed AccountSep 16, 2009
I disagree. While the term Web 2.0 is thrown around too much, I think it did represent the significant shift that happened on the Web. However now that the initial shift has happened, there are a lot more people how know the phrase "Web 2.0" and throw it around only to sound smart in board meeting or whatever. Overall the phrase Web 2.0 is only moronic when used by morons.