Archived
This forum has been archived. Please start a new discussion on GitHub.
(Mis)use of Glacier2
Hi,
I was thinking about trying to use Glacier2 to make a highly available application environment. Here is the idea. Set up two machines identically. Have identical application servers running on both machines. Run a modified Glacier2 on both machines. When Glacier2 sees a message that is mutating, it would forward the request to both machines. When it receives the responses, it sends one of them to /dev/null so the client only sees one response. It also detects the case where only one response comes back in some time. Of course there are locking issues and such to deal with.
I haven't spent time in the Glacier2 code. Is this a reasonable thing to try to do with the application? Would you envision such a mod as difficult?
Thanks for any advice before I get my head into the code.
-- Andrew Bell
andrew.bell.ia@gmail.com
I was thinking about trying to use Glacier2 to make a highly available application environment. Here is the idea. Set up two machines identically. Have identical application servers running on both machines. Run a modified Glacier2 on both machines. When Glacier2 sees a message that is mutating, it would forward the request to both machines. When it receives the responses, it sends one of them to /dev/null so the client only sees one response. It also detects the case where only one response comes back in some time. Of course there are locking issues and such to deal with.
I haven't spent time in the Glacier2 code. Is this a reasonable thing to try to do with the application? Would you envision such a mod as difficult?
Thanks for any advice before I get my head into the code.
-- Andrew Bell
andrew.bell.ia@gmail.com
0