Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perform replication of data for HMIS/CES schemas by creating another postgres RDS and replicating the data there. #247

Open
logicsandeep opened this issue Jan 16, 2017 · 4 comments

Comments

@logicsandeep
Copy link
Contributor

Perform replication of data for HMIS/CES schemas by creating another postgres RDS and replicating the data there.

@eric-jahn
Copy link
Member

eric-jahn commented Jan 17, 2017

Wouldn't it be better to just use Postgres' multi-node feature, if we are going for stability and scalability?

@logicsandeep
Copy link
Contributor Author

Yes, that's what we would like to use. I'm also looking in terms of having 100% replication so that if one node is down we can use another node to get data. And possibly add a load balancer to get the postgres data from the postgres nodes.

@eric-jahn
Copy link
Member

perfect

@eric-jahn eric-jahn added this to the v2.1.0 milestone Apr 21, 2017
@suryayadavalli
Copy link
Contributor

Proposed cloud architecture addresses this availability and replication issue. With this set up , the physical replication of the database is handled on a different zone , automatically handled by AWS, and failover happens automatically to the secondary instance during all the failover scenarios

  • Loss of availability of the master instance
  • Loss of network connectivity to the master instance
  • Compute unit failure on primary
  • Storage failure on primary

More on Multi availability zone here from AWS
https://aws.amazon.com/rds/details/multi-az/

@eric-jahn eric-jahn modified the milestones: v2.2.0 - human service features typically used by hmis systems, v2.1.0 APR reports and virtual private cloud May 3, 2017
@eric-jahn eric-jahn removed this from the v2.2.0 - 2017 HMIS Data Standard milestone Aug 20, 2017
@eric-jahn eric-jahn added this to the 2.7.0 milestone Oct 2, 2017
@eric-jahn eric-jahn removed this from the v2.7 milestone Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants