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

51–59 of 59 posts

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

#51

Post by nevodavid10 »

jitl wrote: post #17
nevodavid10 wrote: post #8

Earlier quoted context omitted.

I think you can def do it on a low scale. You would not need this tech. At least not the Kafka / Timescale feature. It would place nice if you were a bit bigger - a news website, a social media and so on.

How many clicks per second on an item would justify this architecture? Ballpark numbers and napkin math estimates is fine - again it would seem reasonable if justified. If I’m gonna get that many clicks per second, it’s likely I’ll already have my own analytics system, queue system, cache architecture, application database. Why adopt this external code when I’ll spend more work integrating it into my application comp…

My main question was, how many will I have + what the architecture should be for other developers to trust me to handle their load?

In a few years from now. (I am talking about the managed version)

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

#52

Post by nevodavid10 »

worksonmine wrote: post #40
_a9 wrote: post #27

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.

Up- and downvotes without authentication will be abused.

You can use something like fingerprint.com

It's something that I think about. It can be really great (in my opinion)

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

#53

Post by nevodavid10 »

rglullis wrote: post #20
nevodavid10 wrote: post #12

Earlier quoted context omitted.

Can you elaborate on this? ^_^

The point is that this crazy architecture could (perhaps) only be justified if all my backend is outsourced to external serverless points. The moment that I need to have my own backend to manage some data, I can add the item rating data as well and your system becomes more complex than the built-in solution.

I am going to make a lighter version of it! Just redis, websockets and Mongodb!

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

#54

Post by nevodavid10 »

dcsan wrote: post #48
dcsan wrote: post #42

congrats on learning some new tools! it is a bit 'astronaut architected' but you seem to have a history of building stuff and asking for feedback, that will always result in learning fast. hope you got some useful replies here! a much simpler build system that's easy for people to adopt might have a higher chance of getting initial traction, and then you can add the layers only when they're needed. See YAGNI (You Ain…

unless we all got click baited > https://dev.to/nevodavid Technical Content Writing + DISTRIBUTION

That's my other business :) Clickvote is mine also, and I am very serious about it.

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

#55

Post by nevodavid10 »

linuxdude314 wrote: post #38

When designing a tool, scalability should be a feature not a requirement. There isn't so much value in creating scalable tools these days as they exist in abundance. What is rarer and more useful are tools that are easy to use at small scale that work without minimal modification and headaches at scale. Unless you're only running one instance of this, it probably makes sense to scale back immediately otherwise your c…

I was thinking of using something like Upstash for serverless redis and Kafka so it won't be so expensive.

Horizontal scaling will happen in any way if I just use a simple message queue.

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

#56

Post by nevodavid10 »

tomcam wrote: post #35

Congratulations for creating a product that I believe will most certainly find a market. Like the others, I believe you could dramatically simplify the architecture, but mad props for just publishing your MVP, and throwing it to the sharks of HN. It seems very clear to me that many of these sharks have never tried to implement a similar system.

Thank you! I think the idea is innovative and can be expanded. It's really a small small MVP. To see the community adoption.

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

#58

Post by nevodavid10 »

shri_krishna wrote: post #43
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…

Even better is to just use Clickhouse (maybe Kafka if there are lots of inserts and async_insert isn't sufficient) and Postgres.

Thought about Clickhouse without Kafka even because it can handle streams of data.

But now sure what to do on failures.

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

#59

Post by tomas789 »

bastawhiz wrote: post #14
tomas789 wrote: post #11

I love how in the age of good old PHP, Django and alike this would be insanity. But with serverless it makes sense I guess.

Nonsense! You could build this with Django Channels with no problem. There's nothing about this system that makes Django (or really any other framework) a poor choice.

My point was quite the other way around. With those legacy tools it is very simple and most people would just build the feature. Serverless adds more friction if you don’t have a suitable backend. And this makes sense then.
Post reply on HN