0megion

6 ms·

1.
Show HN: Recipery: Self-hosted recipe manager, no database required(recipery.dev)
1 points by 0megion 11d ago|0 comments
2.
by 0megion 19d ago
Hi, developer of Bookhoarder here. I am a big fan of e-readers, specifically Kindle. However, I would like to own my books rather than just having a digital copy on a provider, not knowing if they will allow me to read them in the future. I
3.
Bookhoarder: Open-Source, Self-Hosted ePub Library on Object Storage(bookhoarder.dev)
2 points by 0megion 19d ago|1 comments
4.
by 0megion 24d ago
That is fair. However, the fact that we have this discussion because I wrote the post in English, I wouldn’t reach out to my fellow engineers to discuss the matter this broadly.
5.
by 0megion 24d ago
Maybe I should have added this part. As a non-native English speaker, using AI to write RFCs, ADRs, and internal documentation, my own writing style shifted so much to the direction that my writing seems like AI.
6.
AI and Infrastructure Engineering(omegion.dev)
72 points by 0megion 24d ago|41 comments
7.
by 0megion 1y ago
If requests are already hitting your servers, it’s too late — you’re burning CPU and bandwidth before rejecting. I built Rately to solve this at the edge: set limits by user, IP, or plan (e.g. free = 1k/day, pro = 1M/month) and re
8.
I built a service to make custom rate limiting less painful(rately.dev)
1 points by 0megion 1y ago|0 comments
9.
by 0megion 1y ago
Interesting, but still your Rail app needs to apply the rate limit logic working with Redis, maybe your DB will be protected, but you will still receive the traffic through your network, meaning more ingress cost, along with CPU to process
10.
by 0megion 1y ago
It's already too late if requests are hitting your service. What happens when a customer sends x100 traffic all of a sudden, your Rails backend needs to scale or crash to handle the rate limiting.
11.
by 0megion 1y ago
Correct, pricing would be based on the traffic volume.
12.
by 0megion 1y ago
That is fair. Maybe Proxy mode would be a way to go in this case? Instead of calling another API, you can pass through your requests, and only a small amount can reach your origin.
13.
Testing a new rate-limiting service – feedback welcome
3 points by 0megion 1y ago|9 comments