8 ms·

Oooh, making it a standardized postgres extension (rather than its own compiled fork) is suuuuper-compelling. I've toyed with pipelinedb here and there, but the

by pfooti 10y ago

Oooh, making it a standardized postgres extension (rather than its own compiled fork) is suuuuper-compelling. I've toyed with pipelinedb here and there, but the mental overhead of maintaining it separately from postgres is a little heavy. Even if the benefit is largely psychological, I think this is a great move.

purple-dragon 10y ago
I agree. I would love to deploy this to production, but I have hesitated due to the mental gymnastics and concerns you mentioned.
grammr 10y ago
Hello! I'm Derek, one of the PipelineDB co-founders. The way using PipelineDB feels to users has always been a principal consideration to us and how we make design decisions, so a psychological benefit isn't a second-class citizen in our minds. With so many different tools to choose from nowadays, any friction at all (technical or non-technical) can be a showstopper. We've always strived to make PipelineDB as easy to use as possible, and the extension refactor is the grand finale of that continual effort as we approach 1.0. Thank you for your input, and we hope you you'll find great success with PipelineDB in the future!
- rosser 10y ago
  When this ships as a PostgreSQL extension, it looks like it could very handily solve a problem for which we're currently pilot-testing logical decoding. I look forward to trying it, and would happily explore whether beta testing in a large scale environment (half a million concurrent users) is something my management chain and internal customers would be open to. Thank you for your work!
  - grammr 10y ago
    If you're open to sharing, I'd love to hear more about your potential use case. Please email me!
    - rosser 10y ago
      Your email isn't listed on your profile. Mine is, though. Please do get in touch.
      - justinclift 10y ago
        His GitHub profile has it: :) https://github.com/derekjn
buremba 10y ago
I think it's not just "mental overhead". The main benefit would be able to use PipelineDB with other Postgresql extensions like CitusDB. It will make Postgresql competitor to many Hadoop oriented architectures.

by pfooti 10y ago

purple-dragon 10y ago

I agree. I would love to deploy this to production, but I have hesitated due to the mental gymnastics and concerns you mentioned.

grammr 10y ago

Hello! I'm Derek, one of the PipelineDB co-founders. The way using PipelineDB feels to users has always been a principal consideration to us and how we make design decisions, so a psychological benefit isn't a second-class citizen in our minds. With so many different tools to choose from nowadays, any friction at all (technical or non-technical) can be a showstopper. We've always strived to make PipelineDB as easy to use as possible, and the extension refactor is the grand finale of that continual effort as we approach 1.0. Thank you for your input, and we hope you you'll find great success with PipelineDB in the future!

rosser 10y ago
When this ships as a PostgreSQL extension, it looks like it could very handily solve a problem for which we're currently pilot-testing logical decoding. I look forward to trying it, and would happily explore whether beta testing in a large scale environment (half a million concurrent users) is something my management chain and internal customers would be open to. Thank you for your work!
- grammr 10y ago
  If you're open to sharing, I'd love to hear more about your potential use case. Please email me!
  - rosser 10y ago
    Your email isn't listed on your profile. Mine is, though. Please do get in touch.
    - justinclift 10y ago
      His GitHub profile has it: :) https://github.com/derekjn

buremba 10y ago

I think it's not just "mental overhead". The main benefit would be able to use PipelineDB with other Postgresql extensions like CitusDB. It will make Postgresql competitor to many Hadoop oriented architectures.