Using Redis as a .NET Core Data Store

preview_player
Показать описание
In this episode of On .NET, Todd Gardner walks Christos through how his company is using Redis in their .NET Core application as the main data store. He explains the architecture of the project and shows how they integrate with StackExchange.Redis.

[04:00] - Reviewing the data model
[07:56] - Reviewing the data in Redis
[10:09] - Working with Redis and .NET

Using Redis with .Net C#

Quickstart: Use Azure Cache for Redis with a .NET Core app

Improve session scalability in a .NET Framework ASP.NET web application by using Azure Cache for Redis

StackExchange.Redis on GitHub

Request Metrics

#dotnet #redis
Рекомендации по теме
Комментарии
Автор

Awesom, thanks I at last have a something to show to validate what I;be been trying to convince Architects and Developers about. Thank you Christos, Thank you Todd

ourjamie
Автор

why you store json as value? instead of packing it with lz4 for example

mdp
Автор

I am obviously missing something here. Aren't the log files acting as the data store and Redis acting as a cache containing transformed data originating from the log files?

ronaldwalcott
Автор

Are they running their Redis instances on Linux? I have to install it (Redis itself, not just the Redis client) on Windows

GovernorSilver
Автор

Thank you for this video and important information

manuelgambini
Автор

Would be nice to know how you implement insert in Redis and handle its results. I'm new in Redis just started to implement it in our app. We have a couple of filters so used secondary indexes. To insert key-value and sets I using transactions. Execute returns bool and I first handle it, after I handle all results from StringSetAsync and SetAddAsync. Don't like this anty pattern when instead of Exception returns some results. How did you implement it and handle results?
Don't you afraid that sth can not be inserted?

pavlopaitak
Автор

What if I want these metrics to be processed in my code every x times?

JH-qefu
Автор

after everything we've learned that readability is key to maintainability, now we learn our database columns should be "tc" instead of "totalcount" etc..??? This leads simply to developers becoming irreplaceable because the system is not descriptive enough for new comers to "easily" jump in & figure out to maintain or extend. Back to Terrible idea.

moorzymoores