week 9 – backend API, storing data in MS SQL database

It’s been a good week for my project. I had quite optimistic plans for it, but I realized them almost completely. Maybe there are not many changes in the frontend part, but I set the backend side of the project.
As I announced in the first articles in this series I used .Net 6 for the API controllers and I store data in MS SQL database using Entity Framework Core. I chose this tech stack because I work with these technologies in my daily work.
Therefore, this part of the project went pretty quickly. The only thing I planned to do and haven’t finished yet is the refresh token mechanism.

what did I do last week?

๐Ÿ”ถ made register/login views in angular
๐Ÿ”ถ signing up/ logging in/logging out finished & tested
๐Ÿ”ถ authentication API in .Net 6
๐Ÿ”ถ question management API in .Net
๐Ÿ”ถ storing questions & users in MS SQL (using Entity Framework)

what was the biggest impediment?

  • understanding the authentication mechanism (what are the vulnerabilities and how to avoid them)
  • generating tokens (configuring all needed settings in .Net was not so clear)

what is the plan for next week?

  • implement refresh token
  • fix buttons appearance
  • invent & implement points and reward strategy
  • add user profile component with user settings

time spent

  • from last week
    20h 0m
  • overall
    117h 30m

costs

  • from last week
    0 $
  • overall
    32 $

summary

I’m really happy with what I achieved last week. After the refresh token mechanism is completed, I will try to write down missing key things before deploying the app on azure and going public. There is still some time left until the end of the year…

Related Posts

Leave a Reply

Your email address will not be published.