Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Omnigres: Postgres as a Platform

github.com

Post reply on HN
Print view View original

11–20 of 77 posts

Re: Omnigres: Postgres as a Platform

#11

Post by civilized »

lovasoa wrote: post #6

Nice 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 u…

> the often recommended "good practice" of separating storage and compute.

This gets me thinking... has developer conventional wisdom ever recommended binding things together? Or does it only ever recommend more separation, more abstraction?

Re: Omnigres: Postgres as a Platform

#12

Post by yrashk »

dvasdekis wrote: post #9
dvasdekis wrote: post #8

I 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 :)

Thank you for your kind words! The original dream was indeed a "one box" approach, even when they scale horizontally and to the edge. Perhaps a more accurate depiction of this is a "unified interface".

Re: Omnigres: Postgres as a Platform

#13

Post by yrashk »

anonu wrote: post #7

I 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.

I am aware of kdb, J and others in the space! Love their brevity and ingenuity.

As you rightly point out, the idea behind Omnigres is to make a lot of these concepts available broadly.

Re: Omnigres: Postgres as a Platform

#14

Post by rtpg »

This sort of stuff (and a lot of other popular things) highlights something that I've felt for years: we are still so far away from a good ops story as an industry.

Why would someone use this? Because they only want to deal with "one thing" in production. Dealing with multiple stacks is annoying. People show stuff like kubernetes as a way to handle multiple stacks. That stuff is also complicated.

There is still a huge opportunity for a methodology (accessible to non-operators) to get systems in production easily, where we wouldn't feel the need to force it all into these kinds of models.

Having said all of that, this is pretty fun looking!

Re: Omnigres: Postgres as a Platform

#15

Post by wk_end »

civilized wrote: post #11
lovasoa wrote: post #6

Nice 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 u…

> the often recommended "good practice" of separating storage and compute. This gets me thinking... has developer conventional wisdom ever recommended binding things together? Or does it only ever recommend more separation, more abstraction?

React is a recent example of the “right” thing being less separated than prior conventional wisdom - we’re now mixing JS, often styling, and “HTML” when the historical powers that be demanded separation.

Re: Omnigres: Postgres as a Platform

#17

Post by Inviz »

I did something similar once, but integrated everything RESTful into nginx which connected to postgres directly, which ran triggers with JS. What I didnt like about it is being bound by max connections to postgres, and then blocking postgres thread when running javascript in it. The parallelization story just wasnt competitive enough.

Is this something that omnigres addresses?

Re: Omnigres: Postgres as a Platform

#18

Post by yrashk »

Inviz wrote: post #17

I did something similar once, but integrated everything RESTful into nginx which connected to postgres directly, which ran triggers with JS. What I didnt like about it is being bound by max connections to postgres, and then blocking postgres thread when running javascript in it. The parallelization story just wasnt competitive enough. Is this something that omnigres addresses?

We don't really use connections but a pool of workers to process requests.

Having http server tightly coupled with the database server makes for a responsive combo.

We are still blocking workers, but prototyping improvements that will alleviate this.

Re: Omnigres: Postgres as a Platform

#19

Post by Kinrany »

civilized wrote: post #11
lovasoa wrote: post #6

Nice 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 u…

> the often recommended "good practice" of separating storage and compute. This gets me thinking... has developer conventional wisdom ever recommended binding things together? Or does it only ever recommend more separation, more abstraction?

Every time something is described as opinionated.

Re: Omnigres: Postgres as a Platform

#20

Post by axelthegerman »

a-b wrote: post #16

Omnigress developed a fresh view of the otherwise stalled industry approach to deploying and running software. Edge computing is a way to go!

I didn't read anything about edge computing in the project readme. Deploying a single instance would be the opposite of that.

Unless you mean edge as opposed to mainstream?

Post reply on HN