1) automated failover is too risky, you should just setup monitors that page you and you can do manual failover,
2) if you just write your own client you can build in monitoring, failover, and the required Redis control stuff, and
3) just wait for Redis cluster to be finished - it'll be awesome and solve all your problems.
There has to be someone out there who needed an automated failover solution for HA for Redis other than me.... Any ideas? (If I end up writing my own scripts, I will share them, but man it seems impossible I'm the first person with this need).
- 10MinuteMailFounder, 2006 - present
- Spark::redFounding Partner, 2007 - present
- UltaATG Architect, 2008 - 2011
- AT&TATG Architect
- CingularATG Architect, 2005 - 2007
- AT&T WirelessATG Architect, 2003 - 2005
- Qpass2005 - 2005
- CellExchange2002 - 2003
- ATGATG Architect, 1998 - 2001
- Resource InteractiveATG Architect, 2007 - 2008
- MagicWaiterCo-Founder, 2002 - 2003
- MacMiniServersFounder, 2005 - 2005
I have been working in the Java-based web application space for over fifteen years as a developer, sales engineer, consultant, architect, security specialist, and entrepreneur.
Having worked for years as an architect at ATG, my primary focus is ATG. I have experience working on some of the largest eCommerce websites in the world. I also build web applications using JBoss as well as technologies such as Seam, EJB3, Hibernate, and JSF.
I founded Spark::red a company providing managed hosting for ATG Oracle Commerce applications.
Please read my tech blog to find out more about what I have been up to.
- Boston University
- Phillips Academy at Andover