Go-GRPC-Auth-Microservice VS go-grpc-middleware

Let's try to create closer to real world gRPC microservice with tracing and monitoring 👋: Source code u can find here Core tools used what will be used: 🚀 PostgreSQL as database Redis for sessions and caching Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus

Hello, Those interviews are even crazy for internship. Anyway 1. Try to find a simple CRUD example online. You can check [this](https://tutorialedge.net/golang/go-grpc-beginners-tutorial/) 2. For logging you can check [go-grpc-middleware](https://github.com/grpc-ecosystem/go-grpc-middleware) 3. You can grpc-gateway in case they want some REST endpoints too 4. Use base62 to encode your url. So at least 2 columns in your table **shortenedUrl** and **url** 5. For such a project no need to use an ORM ( it's not advised anyway ). Implement 2 functions, one to insert into the db and the other one to read from the db. Remember to use transaction though 5. For unit tests go with the standard library and mock the 2 functions ( erroneous and valid cases )

Supported middlewares by gRPC framework.

I do some basic validation at the server layer using a GRPC interceptor.

Example auth middleware: https://github.com/grpc-ecosystem/go-grpc-middleware/blob/master/auth/examples_test.go

And initialize our gRPC service, here i used gRPC Middleware repository for unary interceptors:

I found this is very good gRPC Middleware repository, but we easy can create our own, for example logger interceptor: