Project Updates - TODO

[hadeer-r]

Main Edits

• Project decorization
• remove soft delete from M-N relationships and update related APIs and services
• middleware for lastseen
• OAuth register & login (google)
• Edit user, Auth, Comment, User services to use Notification
• support images
• global exception handler
• Performance Optimization: Identify Endpoints for Caching to Reduce DB Load

Testing

Unit Testing

• User service:
  • follow & unfollow
  • current user
  • user by id
  • update password
• Auth Service
  • login
  • register
  • refresh token
  • logout
  • forget & reset password

Integration Testing:

• user APIs
• Auth APIs
• Comments APIs
• Notification APIs

[hadeer-r]

@ziad-ashraf7 @Mahmoud-Ayman-Saleh
I divided all remaining work to small tasks, so it will easy to finish that task a few hours and merge it
so when everyone works on task, just put comment that he will work on it

[hadeer-r]

I will work on lastseen method

[ziad-ashraf7]

Hi @hadeer-r ,
Can you add "Adding Caching Service using Redis" to the TODO ?

I though it would be so efficient if we cached some useful information about responses to improve the performance and reduce database calls.

It can be "Low Priority" for now. but just add it so we don't forget adding it in the future.

[hadeer-r]

Hi @ziad-ashraf7 ,
We do have the Redis Caching Service implemented already. The AddCache method, and the service file itself, are available here:

Backend/AskFm/AskFm.BLL/Services/RedisCacheService.cs

Line 15 in 28cc556

public async Task SetCacheAsync<T>(string key, T value, TimeSpan expirationTime)

Could you please clarify?
Do you mean adding a TODO item to apply caching to a specific responses?

[ziad-ashraf7]

Hi @hadeer-r ,
Sorry for this confusion and unclear description.
What I meant is using the Caching service for the response and endpoint that we can use it on.

for example , there we can cache the GetAll{X} endpoints' responses, so we don't have to go and call the database for each time the user uses the same request (or even the same search queries), unless the cached data is still valid (no update/add on the resources).

I hope this makes things more clear.

[hadeer-r]

Okay, @ziad-ashraf7,

I understand your point. To clarify the implementation process, when we want to cache responses, we will call the setCache method from the caching service and utilize it, similar to how we currently do in the AuthService.cs:
https://github.com/Askfm-clone/Backend/blob/Develop/AskFm/AskFm.BLL/Services/UserIdentityService/AuthService.cs

Since we agree on the principle, I have added a task to the TODO list to remind us to review all endpoints to determine which ones require caching implementation.