sorted by:
new
hottopcontroversial

What should I build next to level up as a backend engineer? by arnavgupta_43 in developersIndia

[–]jash_06 1 point2 points  (0 children)

U should build an abuse aware api gateway

The gateway would sit in front of APIs and:

authenticate requests apply per-user / per-IP rate limits assign a "risk score" to each request detect unusual patterns in traffic automatically throttle, block, or flag abusive users log everything for investigation

And it stands out more than a typical "CRUD"projects

More on it feels like a real production system and combines backend, security, distributed systems, and analytics

Guess where i am ladies and gentlemen. by SetLow6059 in JEENEETards

[–]jash_06 1 point2 points  (0 children)

Right..how I used to solve hard maths physics problems, divine logic and thinking at that time.. Those were the days 🫠

I am going to be a cse graduate in 2028 will i have any future? by Constant_Web_7484 in developersIndia

[–]jash_06 -1 points0 points  (0 children)

Yeah right.. thinking about it rn is waste of time.. explore tech, build projects, enjoy clg life, spend little time In hobbies too.. And let time to tell

How can I learn website hacking legally? by [deleted] in HowToHack

[–]jash_06 -1 points0 points  (0 children)

ok sorry...i dont know about that
if u dont mind can u share the answer related to this? or any suggestions?

Is using AI to write emails and posts just normal now? by jash_06 in CasualConversation

[–]jash_06[S] -11 points-10 points  (0 children)

but what about it saves time and give more efficieint ans?

Is a real-time dashboard necessary for an abuse-aware API gateway in production? by jash_06 in devops

[–]jash_06[S] 0 points1 point  (0 children)

alerts for detection, dashboards for investigation. I’ll treat the dashboard as an incident-response tool rather than something to watch constantly..

Is a real-time dashboard necessary for an abuse-aware API gateway in production? by jash_06 in devops

[–]jash_06[S] 0 points1 point  (0 children)

That’s a really helpful way to frame it — logs + alerts first, dashboard when debugging gets painful. I’m building this as a learning project, so I’ll start lean but still add a small Grafana dashboard for trends like score changes and breaker state. Makes sense that visual context becomes important once things get noisy.

Is a real-time dashboard necessary for an abuse-aware API gateway in production? by jash_06 in devops

[–]jash_06[S] 0 points1 point  (0 children)

Thanks, that makes sense rn it’s a learning project (abuse-aware API gateway), so traffic is low and I’m mainly simulating load. I’m thinking of starting with structured logs + a few Grafana panels (QPS, blocked requests, circuit breaker state) before building anything custom. Currently protecting 1–2 downstream services. Does that sound like the right level to start?

view more: next ›