Course Content
Testing Good Practices, Mocking, Types of Doubles
0/4
Good qualties of unit tests
What is Mocking
How to autowire if we have more then one instance
How to delete category if products to attached with this
Testing demo, annotation and product controller test
0/6
Explanation of java testing folder structure
Test Annotations
How to navigate from normal file to test file
Write first demo test
Product Controller Test
Exception Test
00:00
Auth v/s Auth, Tokens, BCrypt
0/5
Authentication and Authorisation
Authentication Process Flow
Hashing
Bcrypt Encoder
Token
Authentication : Implementing User Service
0/4
Oauth
Step by step guide how to create Sign up
44:52
Step by step guide how to create Sign In
Step by step guide how to Logout
Implementing OAuth 2 authentication using Spring Security
0/2
Spring Security
00:00
Developing Your First Application
00:00
Creating a Payment Microservice Implementing Razorpay
0/5
Step-by-Step Guide to Building a Payment Microservice
48:02
How to Create and Set Up a Payment Service Project in Spring Initializr
Developing a Payment Controller and Service in Spring Boot
Integrating Razorpay Java Client SDK into Your Payment Microservice
How to Implement getStatus in RazorPayGateway for Payment Microservices
Optimizing our APIs using Redis and Kafka for ASync Comm
0/5
Caching introduced here
How to Update the Cache:
Caching in product service
Global cache
Introducing a Cache Layer with Redis
Low Level Design Notes
0/1
Download Notes
11:13
Backend Low Level Design 4
About Lesson
Storing passwords as plain text in a database can pose a serious security risk because anyone with access to the database can see them. To address this, we use a technique called hashing to store passwords securely.

Here's how hashing works:

  • When a user creates an account and sets a password, we take that password and convert it into a hash value using a cryptographic algorithm.
  • This hash value, which is a unique string of characters, is then stored in the database instead of the actual password.
  • When the user tries to log in, we take the password they provide, hash it using the same algorithm, and compare the resulting hash with the one stored in the database.
  • If the hashes match, the login is successful.
While hashing solves the security issue of storing plain text passwords, there’s still a concern. If the same password always generates the same hash, attackers could potentially guess passwords by comparing hashes.

Solve the issue using salting

To mitigate this risk, we use techniques like salting (It can be combination of serverId + Time + email with password), which involves adding a random string of characters to each password before hashing it. This ensures that even if two users have the same password, their hashes will be different.
Previous
Next
Enroll Now