fdw for managing a cluster

[jeromew]

Hello,

I am trying to see how I could use a fdw wrapper to manage a cluster of servers and have all the servers accessible via sql.

I am hesitating on the type of fdw that I should use (I don't even know if this is a good idea). I could use www_fdw and access web services on each servers or I could have each server make believe they are redis servers and use redis_fdw for example.

I was wondering what you think about www_fdw in this use case, since you started this project 2 years ago and must have a good idea of the pros&cons of this approach.

compared to the web services in the example of www_fdw, my web services could also be writable ("start a service", "change this configuration", ..) and I would probably need to be able to POST or PUT variables to the services.

Anyway, I would be very interested in knowing more about your experience with www_fdw. From the outside it looks very powerful to be able to wrap web services like you did. How does it look like from the inside after 2 years of usage ;-) ?

[cyga]

Hello,

take a look into: http://lwn.net/Articles/550418/ http://www.postgresql.org/docs/current/static/postgres-fdw.html

:)

2014-10-17 22:16 GMT+07:00 jeromew notifications@github.com:

Hello,

I am trying to see how I could use a fdw wrapper to manage a cluster of servers and have all the servers accessible via sql.

I am hesitating on the type of fdw that I should use (I don't even know if this is a good idea). I could use www_fdw and access web services on each servers or I could have each server make believe they are redis servers and use redis_fdw for example.

I was wondering what you think about www_fdw in this use case, since you started this project 2 years ago and must have a good idea of the pros&cons of this approach.

compared to the web services in the example of www_fdw, my web services could also be writable ("start a service", "change this configuration", ..) and I would probably need to be able to POST or PUT variables to the services.

Anyway, I would be very interested in knowing more about your experience with www_fdw. From the outside it looks very powerful to be able to wrap web services like you did. How does it look like from the inside after 2 years of usage ;-) ?

Reply to this email directly or view it on GitHub https://github.com/cyga/www_fdw/issues/6.

Alexandr Sudakov Software Developer email: cygakoB@gmail.com skype: asudakov

[jeromew]

@cyga I checked the thank you. To federate several postgres instances, postgres_fdw is the easy answer.

I also read http://snowman.net/slides/pgfdw_sharding.pdf which has some interesting info.

but does that mean you would not recommend using www_fdw for a farm of applications that are not postgres instances ?

www_fdw seem very elegant in my use case, but I was wondering what is your feedback 2 years after creating www_fdw (if you can share some elements).

[cyga]

I would recommend it for web applications. www_fdw is very flexible.

2014-10-21 21:35 GMT+07:00 jeromew notifications@github.com:

@cyga https://github.com/cyga I checked the thank you. To federate several postgres instances, postgres_fdw is the easy answer.

I also read http://snowman.net/slides/pgfdw_sharding.pdf which has some interesting info.

but does that mean you would not recommend using www_fdw for a farm of applications that are not postgres instances ?

www_fdw seem very elegant in my use case, but I was wondering what is your feedback 2 years after creating www_fdw (if you can share some elements).

Reply to this email directly or view it on GitHub https://github.com/cyga/www_fdw/issues/6#issuecomment-59937125.

Alexandr Sudakov Software Developer email: cygakoB@gmail.com skype: asudakov

[jeromew]

ok thank you. I will try and use it while I begin to understand the pros & cons of fdw for the management of a farm.