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

add ElephantSQL to OpenShift doc #603

Merged
merged 2 commits into from
Feb 8, 2019

Conversation

vorburger
Copy link
Contributor

mostly just because it was on https://alf.io/tutorials/openshift/
which I just removed via alfio-event/alf.io-website#7

@cbellone

@coveralls
Copy link

coveralls commented Feb 7, 2019

Coverage Status

Coverage remained the same at 51.383% when pulling d6b97dd on vorburger:patch-2 into 8d92818 on alfio-event:1.x-maintenance.


## Postgres database alternative

Instead of the containerized Postgres which the YAML (above) sets up on your OpenShift, you could also consider using an external managed Postgres as a Service, e.g. from https://www.elephantsql.com. (You'd probably want to test performance due to the higher latency between the Alf.io app and the DB in this approach.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the last part to:
You'd probably want to deploy your ElephantSQL instance as close as possible to your Openshift cluster, in order to reduce latency
?
ElephantSQL's servers are deployed in almost all AWS/GCP/Azure regions, so it's just a matter of choosing wisely :-)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@cbellone cbellone merged commit 17ec95e into alfio-event:1.x-maintenance Feb 8, 2019
@cbellone
Copy link
Member

cbellone commented Feb 8, 2019

thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants