Fabulously40 Architecture
April 26, 2009
For those interested in how we run Fabulously40.
1. Single server, OpenSolaris / 8Gigs RAM / Quad Xeon x5355 / 100Mbit line.
2. Static and dynamic data cached up front on varnish
3. Even though Nginx can handle L7 load balancing, Perlbal offers better flexibility with its plugin system
4. Jetty application servers easily scale out by using memcached as the session store
5. Write intensive operations are done asynchronously via the ActiveMQ message store system
6. One PostgreSQL database on RAID1 with a hot standby database on a third disk.
The application can do 6,000+req/sec and 80-120req/sec without the varnish cache. The platform uses Wicket, Hibernate and Spring for it’s internals.
There you have it.
Nice architecture, you inspired me with this
THX.
Nice architecture, you inspired me with this
THX.
Looks like the chart needs an update (- varnish), but interesting take with your ASF stack.
Why having a Hot Standby and not using something similar like MYSQL PRoxy where you can have the READS from both servers and the writes to 1 that way you can have more power?