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

PostgreSQL support #331

Closed
sonicaghi opened this issue Jun 12, 2015 · 118 comments
Closed

PostgreSQL support #331

sonicaghi opened this issue Jun 12, 2015 · 118 comments
Assignees

Comments

@sonicaghi
Copy link
Member

We should support other datastores than Cassandra which is primarily aimed at users who want to benefit from its distribution capabilities.

Support for PostgreSQL seems the best candidate for the second datastore, due to its popularity, availability on Amazon RDS and reliability. It is also a very good fit for Kong due to its relational nature.

@sonicaghi
Copy link
Member Author

Related to #183

@thorstenz
Copy link

+1 for PostgreSQL support.
very good experience with the jsonb datatype.

@thibaultcha thibaultcha changed the title PostgreSQL support [request] PostgreSQL support Jun 26, 2015
@vishalraina
Copy link

+1

5 similar comments
@bhameyie
Copy link

bhameyie commented Jul 1, 2015

+1

@MattCollinge
Copy link

+1

@skippy
Copy link

skippy commented Jul 2, 2015

+1

@wsimmonds
Copy link

+1

@obsidienne
Copy link

+1

@lucamaraschi
Copy link

👍 👍

@sent-hil
Copy link

👍

3 similar comments
@matti
Copy link

matti commented Jul 10, 2015

👍

@ahmadnassri
Copy link
Contributor

👍

@vivekfantain
Copy link

+1

@owahlen
Copy link

owahlen commented Jul 17, 2015

+1

6 similar comments
@coreybutler
Copy link

+1

@ngbinh
Copy link

ngbinh commented Jul 24, 2015

👍

@bigpg
Copy link

bigpg commented Jul 30, 2015

+1

@udleinati
Copy link

+1

@avtar
Copy link

avtar commented Aug 4, 2015

👍

@vwal
Copy link

vwal commented Aug 10, 2015

+1

@bkleef
Copy link

bkleef commented Aug 20, 2015

+1

3 similar comments
@edurdias
Copy link

+1

@devton
Copy link

devton commented Aug 23, 2015

+1

@mgooty
Copy link

mgooty commented Aug 27, 2015

+1

@RolfKoenders
Copy link

We are using 9.4 as well, on RDS.

@pklingem
Copy link

9.4 is great for us.

@C4
Copy link

C4 commented Jan 29, 2016

Like others, Not using Postgres right now. But something RDS backed would be awesome.

@lindo-jmm
Copy link

Not on AWS (Azure), but I have 9.5 running on a server. Love it!

@nhuray
Copy link

nhuray commented Jan 31, 2016

+1

@kenwarner
Copy link

9.4 on RDS is our use case as well.

@dempe
Copy link

dempe commented Feb 2, 2016

👍 Any version would be fine for us.

@protetore
Copy link

We're using 9.3 on RDS.

@stramel
Copy link

stramel commented Feb 4, 2016

+1, RDS would be great as well

@derrickburns
Copy link

👍

@shaikhfaisal
Copy link

+1 RDS support would be awesome

@mjhlobdell
Copy link

+1

@lsmith77
Copy link

@thibaultcha is there an ETA? also is there already a PR to try out your current state?

@jkwong
Copy link

jkwong commented Feb 14, 2016

+1

6 similar comments
@sathyavijayan
Copy link

+1

@eseres
Copy link

eseres commented Feb 16, 2016

+1

@bramswenson
Copy link

👍

@gianlucatomasino
Copy link

+1

@nickmcintyre
Copy link

+1

@indigostar-kr
Copy link

+1

@jaceq
Copy link

jaceq commented Mar 1, 2016

Is there maybe any update on this topic?

@BrianHutchison
Copy link

+1 for Amazon DynamoDB.

@thibaultcha
Copy link
Member

Hey everyone,

The implementation is almost complete, the branch now lives in this repository (See feature/postgres). As planned, Postgres 9.4 is supported so Amazon RDS should be supported as well, I briefly played with it but it needs to be tested more in-depth once the implementation is complete. Btw, testers are welcome here!

What is missing:
  • Full support for OAuth2 and clustering. Right now those implementations relied on Cassandra rows with TTLs, so right now with Postgres, things don't expire as they would do with Cassandra. This should soon be resolved. This blocks production usage but not simple testing of the feature.
  • Support for SSL connections between Kong and Postgres. As of now, a Pull Request is pending at feat: implement support for SSL connection leafo/pgmoon#24 with support for it. If it gets approved, that should be resolved too.
  • A lot of documentation updates!
How to test it (if you want to try it out or just a glimpse of how to use it):
  • Get your hands on a 9.4+ server
  • Create a database, (maybe a user too?), let's say kong
  • Use the feature/postgres branch of Kong (you must have a source install for this)
  • Update your Kong configuration:
# be careful about your YAML formatting
database: postgres
postgres:
  host: "127.0.0.1"
  port: 5432
  user: kong
  database: kong

As usual, migrations should run from kong start, but as a reminder and just in case, here are some tips:

Reset the database with (careful, you'll lose all data):

$ kong migrations reset --config kong.yml

Run the migrations manually with:

$ kong migrations up --config kong.yml

If needed, list your migrations for debug purposes with:

$ kong migrations list --config kong.yml

If you test it, feel free to report any issues (please not here, but in a new issue in this repo) :)

Thank you all for your patience!

@geovanisouza92
Copy link

+1

@Kong Kong locked and limited conversation to collaborators Mar 7, 2016
@subnetmarco
Copy link
Member

This feature will land in v0.8.

@thibaultcha thibaultcha removed this from the Mar 2016 milestone Apr 11, 2016
@subnetmarco
Copy link
Member

You can play with v0.8.0 with Postgres support at https://github.com/Mashape/kong/releases/tag/0.8.0 - we will update Docker and the website soon.

@subnetmarco
Copy link
Member

Kong 0.8.0 announced: http://blog.mashape.com/announcing-kong-0-8-0-with-postgresql-support/

Enjoy :)

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

No branches or pull requests