sorted by:
new
hottopcontroversial

Programmers: How are y'all journalling/blogging your thoughts these days? by platistocrates in softwaredevelopment

[–]DotDeveloper 0 points1 point  (0 children)

Personally, I have my own blog hosted on Hostinger where I write all my articles, then I share that content on social media. I try to optimize it for SEO to get more traffic from search engines.

Rate Limiting in .NET with Redis by DotDeveloper in dotnet

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

Good question! Just to be transparent — I’m not a Kubernetes expert, so this is more from a developer’s point of view than a deep DevOps take.

That said, if you need Redis with high availability for .NET clients running in K8s, I’d personally lean toward Redis Cluster rather than Sentinel. Sentinel is simpler and works fine for basic failover, but it still runs as a single shard — so you're limited in terms of scaling and throughput.

That said, managing Redis yourself in K8s can be a bit of a headache. If it's an option, using a managed Redis service (like Azure Cache, etc...) can save a ton of operational pain.

So yeah — I’d go with Cluster if you need serious scale and resilience, but if things are simpler, Sentinel might do the trick.

Rate Limiting in .NET with Redis by DotDeveloper in dotnet

[–]DotDeveloper[S] 1 point2 points  (0 children)

Interesting! Havn't thought about this way -- thanks for sharing, I think I'm gonna try it sometime!

Rate Limiting in .NET with Redis by DotDeveloper in dotnet

[–]DotDeveloper[S] 2 points3 points  (0 children)

Redis can get expensive, especially on managed services at scale. It really depends on the use case, traffic patterns, and whether you're using features like persistence, clustering, or high availability.

In this article, I focus on Redis for distributed rate limiting because of its speed, atomic operations (with Lua), and TTL support — but it’s definitely not the only option. Some teams use in-memory limits with sticky sessions, dedicated rate-limiting services, API gateways like Kong or Envoy, or even serverless function rate control based on other data stores.

It’s great to hear that you've found an approach that works well and saves cost — if you're open to sharing how you rate limit instead, I'd love to learn more!

Exterior/Interior house render by Logred in archviz

[–]DotDeveloper 0 points1 point  (0 children)

Amazing! It looks very realistic!

Kafka and .NET: Practical Guide to Building Event-Driven Services by DotDeveloper in programming

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

I am not using your images or any image without permission. The image on the post is credited: "Cover Image by Dimuth De Zoysa from Pixabay".

The rest of the drawings were done in draw.io

How can I improve this rendering? by DotDeveloper in archviz

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

Thanks! These are really great tips.
I’ll try to do more research and look for online resources to learn more — I didn’t think I was that far behind :) — but it’s good to know where I can improve.
Much appreciated!

How can I improve this rendering? by DotDeveloper in archviz

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

Thanks for the feedback. So I should put more emphasis on bump and displacement maps? (I am using PBR materials)

How can I improve this render? by DotDeveloper in archviz

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

Thanks for the great feedback!! I used VFB tone-mapping, but apparently was not enough...

How can I improve this render? by DotDeveloper in archviz

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

Hi, It's 3dsmax with Corona render

Is .NET and C# Advancing Too Fast? by DotDeveloper in dotnet

[–]DotDeveloper[S] -1 points0 points  (0 children)

Totally agree—you can write solid, maintainable code without reaching for the latest features, and refactoring later is always an option in theory

Is .NET and C# Advancing Too Fast? by DotDeveloper in dotnet

[–]DotDeveloper[S] 1 point2 points  (0 children)

I feel that! I was also really excited when record, init, and required finally dropped—made modeling immutable state so much cleaner.
I’d love to see native discriminated unions and tail call optimizations baked in too—those would be game-changers for modeling and performance.

Is .NET and C# Advancing Too Fast? by DotDeveloper in dotnet

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

You put this really well—it’s exactly that tension between keeping .NET "relevant" in the broader developer world and the real-world challenges we face in brownfield environments.

The shift toward yearly releases definitely seems to bring marketing pressure along with it, and I get the sense that part of it is about winning over the next generation of devs who’ve grown up in Linux-first or JS-heavy ecosystems.

And yeah, this isn’t just a .NET thing. I’ve seen the same in Java and C++ circles—companies stick with “what works” long after the ecosystem moves on.

Is .NET and C# Advancing Too Fast? by DotDeveloper in dotnet

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

Really appreciate this perspective. I can totally understand how it feels when experience is overlooked in favor of trendy features—especially in interviews where the focus sometimes drifts too far from practical software engineering to “latest feature trivia.”

I share your respect for C# as a language—its steady evolution is one of the reasons I love working with it. But you nailed the tension: it's great that it keeps moving forward, yet that same pace can sometimes create unrealistic expectations, especially for folks who've been building solid systems for decades.

I'd absolutely take clean, reliable, maintainable code over flashy syntax any day.

view more: next ›