|
From: Michael P. <mic...@gm...> - 2014-03-21 11:52:33
|
On Fri, Mar 21, 2014 at 2:08 PM, Juned Khan <jkh...@gm...> wrote: > Hi All, > > I have very large application, as of now i am using MySQL but i want to > convert it into postgre-xc. postgres-xc. By the way, is there any reason why you are *not* considering PostgreSQL as well? > 1) What is the minimum server requirement for this application ? There is no real *minimum* requirement AFAIK. However, coupling 1 Datanode and 1 Coordinator per server/VM could be useful to minimize network latency on queries. > 2) pgxc will be able to handle 500 concurrent calls on server ? Well yes, but a single Postgres server is able to handle that nicely as well if coupled with a connection pooler. I don't see much why multi-master is a requirement for such a low-number though as you seem to mean in your question. > 3) is there any parameter where i can define maximum connection ? max_connections on each Coordinator/Datanode * number of nodes. You could as well define different values of max_connections per node. > 4) If server crashes then i how to get data back. how to have back up > existing data ? This is a vast question, and without providing any details about what you are looking for in terms of backup and recovery strategy it is hard to guess anything but... This problem is similar to Postgres itself, except that in this case you need to manage N nodes and not 1. Just seeing your email and if you have a requirement with 500 concurrent connections, you might live happily with PostgreSQL + pgbouncer. Regards, -- Michael |