Omnigres: Postgres as a Platform
github.com
Omnigres: Postgres as a Platform
1–10 of 77 posts
Re: Omnigres: Postgres as a Platform
#2Cool project! About a decade ago, I had a job that involved entering data into an Oracle-based equivalent of this. I wish I could remember what it was, called but perhaps it is better for such a monster to remain nothing more than a myth.
Re: Omnigres: Postgres as a Platform
#3Cool project! About a decade ago, I had a job that involved entering data into an Oracle-based equivalent of this. I wish I could remember what it was, called but perhaps it is better for such a monster to remain nothing more than a myth.
Author here. Thanks for the feedback!
The intention we have is to take what's right with the colocation approach and take the learnings of what was wrong with those before (such as the above or Illustra).
Essentially, we're aiming create a modern polyglot runtime that has an embedded database with all its functionality (Postgres), with a contemporary, lightweight D3X.
Re: Omnigres: Postgres as a Platform
#4Cool project! About a decade ago, I had a job that involved entering data into an Oracle-based equivalent of this. I wish I could remember what it was, called but perhaps it is better for such a monster to remain nothing more than a myth.
CouchDB also tries to do something similar (natively hosting webapps close to a DB good at replication between replicas). https://guide.couchdb.org/draft/standalone.html
Re: Omnigres: Postgres as a Platform
#5Cool project! About a decade ago, I had a job that involved entering data into an Oracle-based equivalent of this. I wish I could remember what it was, called but perhaps it is better for such a monster to remain nothing more than a myth.
You are probably thinking of this: https://apex.oracle.com/en/
Re: Omnigres: Postgres as a Platform
#6Nice to see Omnigres trending on hn; congratulations Yurii!
The project is interesting, and thought provoking, because it goes against the often recommended "good practice" of separating storage and compute. Doing the exact opposite has a lot to offer in terms of performance, simplicity, and speed of development.
I am currently also working on a database-first web application framework [1], with different goals and use cases, and I bet we'll see more of these in the future.
Re: Omnigres: Postgres as a Platform
#7I saw omnigres mentioned on a shakti mailing list. Many of these concepts have been around with k (kdb) and some other APL-like languages for some time. But Postgres will give these concepts a much broader appeal.
Re: Omnigres: Postgres as a Platform
#8I was interested in how you do authentication, but currently the 'Omni_web' link & readme is missing. Suggest you could use the pgjwt[0] approach for this for simple logins in the short term, but supporting OpenID Connect would be a larger engineering effort.
Re: Omnigres: Postgres as a Platform
#9I was interested in how you do authentication, but currently the 'Omni_web' link & readme is missing. Suggest you could use the pgjwt[0] approach for this for simple logins in the short term, but supporting OpenID Connect would be a larger engineering effort. [0] https://github.com/michelp/pgjwt
Also forgot to say, love the project and love the objectives! Allowing Postgres to do it all means so much from a server management perspective - imagine not having to manage any redundancy/performance/analysis outside of the health of the Postgres box - fantastic :)
Re: Omnigres: Postgres as a Platform
#10I was interested in how you do authentication, but currently the 'Omni_web' link & readme is missing. Suggest you could use the pgjwt[0] approach for this for simple logins in the short term, but supporting OpenID Connect would be a larger engineering effort. [0] https://github.com/michelp/pgjwt
The current approach employed by Omnigres users is good old sessions (since latency to the database is non-existent) and omni_txn's transactional variables (https://docs.omnigres.org/omni_txn/variables/) to store session-related data.
This way we don't need to handle the difficult parts of JWT (forced expiration, etc.) and the mental model becomes rather simple.