PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
1–10 of 34 posts
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#2Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#3Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
Personally I find myself looking at these and thinking "Why?"
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#4I need a simple rest json store, and this could come handy. I'm using openkeyval right now, but they have a value size limit much too low (which seems to be a bug).
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#5Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
Personally I find myself looking at these and thinking "Why?"
It's called Hacker News and not Practical News for a reason
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#6Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
>Web 3.0
Is that what we're calling this whole 30 lines of javascript, mongo and redis behind the WAN, dynamic language runtime inside the DB era?
Cool.
EDIT: saying that, some kind of featureful document store implementation inside postgres seems inevitable. Isn't that all going to be hstore-based though, what with the new stuff coming in 9.4? I thought the json type was meant to be kind of a stopgap until the full hstore functionality is finished, ie. nesting?
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#7Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
>Web 3.0 Is that what we're calling this whole 30 lines of javascript, mongo and redis behind the WAN, dynamic language runtime inside the DB era? Cool. EDIT: saying that, some kind of featureful document store implementation inside postgres seems inevitable. Isn't that all going to be hstore-based though, what with the new stuff coming in 9.4? I thought the json type was meant to be kind of a stopgap until the full…
You didn't get the memo?
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#8Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
Personally I find myself looking at these and thinking "Why?"
The main motivation is to use the same set of npm-managed modules for backend and frontend model+logic.
A secondary motivation is using two familiar APIs — MongoLab and Firebase — to access existing PostgreSQL databases.
(We're using this in production at Socialtext and g0v.tw.)
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#9Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
Web 3.0 is the semantic web, thank you very much.
Re: PgREST: Node.js in the Database, compatible with MongoLab and Firebase API
#10Looks quite interesting, but I can't help but admit some of these Web 3.0 solutions are getting a bit ridiculous nowadays, especially when it comes to data storage and processing.
>Web 3.0 Is that what we're calling this whole 30 lines of javascript, mongo and redis behind the WAN, dynamic language runtime inside the DB era? Cool. EDIT: saying that, some kind of featureful document store implementation inside postgres seems inevitable. Isn't that all going to be hstore-based though, what with the new stuff coming in 9.4? I thought the json type was meant to be kind of a stopgap until the full…
Yup. Nested hstore and JSON are going to be semantically equivalent ("cast" works both ways), and PgREST will support them equally once 9.4 is released.
PgREST also comes with a shim JSON type for Postgres version 9.1 and earlier, so the column type implementation is mostly hidden from the user.