Strangely had a feeling of knowing Rust before working in it, and what I refer here is mostly the aware presence that you sense on in working in it, the trigger realization was the absence of ; on the last line of return. Before that, my experience of go was like going with the flow and just doing it simple enough without any over engineering and honestly went fast. But Rust says wake up and pay attention to what you are doing now with awareness. So made my build.rs to generate my code from .proto files and implemented the generated trait for my ID service and slowly with updating Cargo.toml file with packages for the purposes like database connection queries execute mostly. The compiler of course tells you a lot of what you have to do yet within Visual Studio Code popups where easy to solve at a beginner level, moving forward into it to become at ease with it comes naturally as you develop code still I don’t know if is worth refactoring my service from go to rust, for now my reasoning is mostly out of valuable insights from the internet about it and certainly go handles gracefully my id service functionality. So I think performance is not a real motive because go is strong enough for my service, it is the resonance of the language and experience poured into the code that I think brings value and a good reason to refactor.

Yes, is not a big deal service size so it can be in rust for the sake of getting into the vibe of coding in it so balance is more towards refactoring because of small codebase ( buf protos ), I also externalized my code into a small library for common use. Thank you for reading. You can leave comments bellow.