go-grpc-middleware VS pam

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:

> It's funny how people keep reinventing things.

That's not exactly fair. The entire point of this exercise is to move away from C code, by implementing it in a memory safe language (Go).

Since PAM uses shared-libraries to operate, that's fundamentally incompatible here (unless you use some CGO like in https://github.com/msteinert/pam) so implementing auth via Caddy's module system is the way to go for this project.