Re:Ask HN: Best practices for server redundancy?
by olefoo on Tuesday January 26, 2010 @02:47AM
(#1077325)
The fix in most cases is having a shared session-store (memchached usually) that the front-end instances share. It's not that painful to retrofit it if you know the software.
Re:Ask HN: Best practices for server redundancy?
by blasdel on Monday January 25, 2010 @10:07AM
(#1075214)
http://spreecommerce.com is the best I could find, I've recently been customizing it for a client.
Re:Ask HN: Best practices for server redundancy?
by thaumaturgy on Monday January 25, 2010 @03:11PM
(#1076018)
Thanks for the link! Looks like I finally have an excuse to learn Ruby.
As a tangent: guys, current ecommerce packages really, really suck. I've had a couple of ecommerce jobs recently, and for one client in particular, had to evaluate most of the field of both free and commercial offerings. They're almost uniformly horrible. Is there anybody willing to take a crack at doing it better?
I suggested round-robin DNS over a reverse proxy because reverse proxies (and similar services, like OpenBGPd) still have a single point of failure in the front-end. No matter what you do, it can still go down, and then all that back-end redundancy does squat.