I’d recommend looking into HAProxy: http://www.haproxy.org/ it’s designed explicitly for the task of proxying a single address to multiple backend servers, providing failover when a node goes down. you’d not have to implement this complexity in your application layer.
Huabin Zheng <[email protected]> wrote: > Hi buddies, > > I want to configure multiple backend servers in sqlalchemy to solve > single point fault. But it seems that there's no direct way. Pooling document > <http://docs.sqlalchemy.org/en/latest/core/pooling.html> gives me some hints > that I can give it a custom connection Creator, so I can set multiple > backends in the Creator and try the next backend if the previous failed. BUT, > I found that dialect, pool, and engine are tightly bindings, so there may be > problems in my solution. > > So what's the write way to use multiple backend servers? Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/sqlalchemy > <http://groups.google.com/group/sqlalchemy>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
