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

Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

github.com

Post reply on HN
Print view View original

21–30 of 59 posts

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#21

Post by bastawhiz »

nevodavid10 wrote: post #16
bastawhiz wrote: post #13

Earlier quoted context omitted.

> It would place nice if you were a bit bigger - a news website, a social media and so on. How big do you think is "big"? I run a system that handles about 3k requests per second (~1:100 writes to reads). No caching, no Redis, just Postgres. One master and a hot standby for failover. It sits around 25% CPU, and most of that is from opening and closing connections rather than queries. There's an important lesson in av…

It's not a big problem to create another version without Kafka, and use Postgres :) What do you think about the idea?

I don't want to tell you what the right answer is for your project. But my dad always said "Use the right tool for the job." And if you don't know what tool is right, test some tools and see which one works best.

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#24

Post by klysm »

bastawhiz wrote: post #9

Why do you need Kafka, Redis, Mongo, AND Postgres? Arguably it could all be done with Postgres or Redis: both have great pubsub implementations. But what could you possibly need two databases for and a queue implementation alongside a popular backend for queues? I don't mean to criticize, but the complexity of this is what I'd expect for something handling hundreds if not thousands of qps. Even then I'd expect you co…

That is an absurd set of technologies to choose. The cost of having multiple persistent backends is so high I’ve never understood the motivation.

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#25

Post by upon_drumhead »

nevodavid10 wrote: post #10
bastawhiz wrote: post #9

Why do you need Kafka, Redis, Mongo, AND Postgres? Arguably it could all be done with Postgres or Redis: both have great pubsub implementations. But what could you possibly need two databases for and a queue implementation alongside a popular backend for queues? I don't mean to criticize, but the complexity of this is what I'd expect for something handling hundreds if not thousands of qps. Even then I'd expect you co…

As for Postgres, I chose Timescale because you can easily change it at any time for Postgres. I plan to have it as a managed service in the future, which means that it will hold a lot of clients - some big, some small. But I think I should def make another smaller version without Kafka and Timescale.

You chose timescale because you can swap it out for Postgres? Why not start with Postgres then? Is there anything timescale provides that is beneficial over Postgres?

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#26

Post by badtuple »

bee_rider wrote: post #18
nevodavid10 wrote: post #10

Earlier quoted context omitted.

As for Postgres, I chose Timescale because you can easily change it at any time for Postgres. I plan to have it as a managed service in the future, which means that it will hold a lot of clients - some big, some small. But I think I should def make another smaller version without Kafka and Timescale.

When it is a managed service, will a single individual be feeding into a single sort of taste profile over multiple sites? Actually am I crazy to thing that wouldn’t be the worst thing in the world? Tracking people across multiple sites without their informed consent is of course totally unethical spying, but if it is clear that they are consciously interacting with UI like yours and they know it is shared, that does…

It's hard enough to view the content I want to see when everyone has "smart" content feeds shoving ads in my face. I work hard to isolate what I look at on Amazon from what I see on YouTube so marketers don't ruin the little bits of the web I'm able to enjoy intentionally. Creating cross-site bleed of account information behind the scenes just makes everything worse for the user who can no longer drive your app...they just have to plop in and let it drive them.

You handwaved the idea of consent by saying it's "clear" to the user. But if there isn't a way to opt out then consent isn't addressed at all.

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#27

Post by _a9 »

I've been looking for something to integrate in my site that just lets unauthed users to add upvotes, downvotes, and maybe some extra ones like 'recommend' or a few general ones like 'cat/dog'. Dont need any alaytics or extras.

Are there any recommended good self-hosted alternatives? This looks nice but requires quite the stack of services.

Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context

#30

Post by ransom1538 »

bastawhiz wrote: post #9

Why do you need Kafka, Redis, Mongo, AND Postgres? Arguably it could all be done with Postgres or Redis: both have great pubsub implementations. But what could you possibly need two databases for and a queue implementation alongside a popular backend for queues? I don't mean to criticize, but the complexity of this is what I'd expect for something handling hundreds if not thousands of qps. Even then I'd expect you co…

[flagged]
Post reply on HN