Large Scale Web Apps Built on Open Source 213
prostoalex writes "Brad Fitzpatrick presented at OSCON with on overview of his little project. Interesting facts about the evolution of the Livejournal back-end architecture."
Saliva causes cancer, but only if swallowed in small amounts over a long period of time. -- George Carlin
Java, Tomcat, Apache on UNIX (Score:2, Interesting)
We are using Oracle as the database, and Solaris as the UNIX, but we could be using MySQL and Linux.
In fact, we are investigating that right now
Re:Java, Tomcat, Apache on UNIX (Score:5, Interesting)
Porn (Score:5, Interesting)
Re:Java, Tomcat, Apache on UNIX (Score:3, Interesting)
That's 100% open source, people... and we are talking large corporate intraweb apps and such.
I work mostly with financial institutions... they prefer IBM backed Linux servers with WebSphere... but still like eclipse (or WSAD, which is eclipse with a Websphere test server plugin), and a commercial DB (oracle, DB2, or informix are popular)... but they still use frameworks like struts, tapestry, spring, and hibernate... all open source.
Re:Salesforce.com (Score:1, Interesting)
Ehhmmm, from the BEA testomnial page..
"Salesforce.com is thrilled to be leveraging WebLogic Workshop 8.1 as an integrated part of our sforce client/service architecture. Using the extreme power of BEA WebLogic Workshop will enable us to make sforce available and accessible to the huge community of mainstream application developers and a wider spectrum of enterprise-class application projects on the industry leading BEA WebLogic Enterprise Platform. I could not imagine a more important combination than BEA and salesforce.com."
- Marc Benioff
Chairman and CEO
salesforce.com
Re:Uh, the Web itself (Score:2, Interesting)
The LJ folks faced scaling problems and had financial limits on how much money they could throw at the problem. So they used smarts and OS software instead of huge piles of money. They also built some new tools that are OS themselves, thus contributing back to the community (I hate that phrase, but this is Slashdot).
The presentation is actually interesting technically, and good news for Linux/MySQL/Perl/etc.
(I guess what I'm saying is that I didn't see a huge call for sarcasm).
Re:Livejournal Images (Score:3, Interesting)
Re:Get a clue (Score:1, Interesting)
It still is a very segregated system with tons and tons of front-end boxes that each do specific things. All the "magic" of Amazon happens in Java and C++ anyway.
Re:Large scale? (Score:5, Interesting)
Anyway, those are only the number of entries being posted. For every entry being posted, there are a ton of inserts actually going on:
* log2 table to contain some metadata about the entry
* logtext2 table to contain the actual text
* logprop2 table (multiple rows, 3-5) containing other metadata about entry
So, four times the traffic, about 6 inserts each, 2400 updates per second--and that's just for posting entries. We get a lot more traffic from people posting comments (which also do 3 or 4 update/inserts each comment), plus people editing their userinfo, uploading new userpics,
While LiveJournal definitely isn't a huge site, it's not a lightweight, and definitely doing pretty good for having around 80 machines and doing 30-40 million fully dynamic page views a day.
What about Livejournal? (Score:4, Interesting)
Re:Get a clue (Score:2, Interesting)
I was thinking mostly of Sybase Replication Server combined with Sybase ASE or Oracle 10g/Oracle Clustering, things that would go really, really nicely in the environment and workload the LiveJournal folk are experiencing.