Omegachads just use the standard lib bruh. Im about done with the basic version of my first web server with some authentication. Im sure once i turn it into a big project, ill eat the crow.
REST is easier to inspect since it’s a text protocol but you use more resources than you have to. GRPC abstracts a lot of stuff away but when things break it’s painful (and once your protobuf is written you have to be careful with changes for bc). Having an api schema / protobuf is helpful to get the picture of the system tho 🤷
gRPC web is now in a fairly good place so you can use those types on the frontend just be aware that many hosting providers dont support the H2 which is required.
I agree with everything you just said. So many people are lying to their audience by lying to them about "take this course" and you're going to make 100k a year with no experience/degree. Recruiting teams will laugh you out the building. I issue that there are so many of these individuals taking advantage of these beginners. I want to make an actual product to teach coding/ project building and make it enjoyable.
Some squads at work started to use it expecting more performance, but that's not where they really got improvements. Anyway, now we are using Istio for canary deployment and have integrations with other clusters and these microservices are being refactored.
I would definitely say that if you are going to use gRPC int he same way as you would use standard APIs then yes, the complexity is not worth it. But what if I want to do bidirectional streaming for example? I would assume in use cases like that it would be ok solution. But using it in the same way as APIs i.e. send request and get response is probably not worth it.
@MelkyDev: will you also have a look out the 'VSCode Neovim' [by A. Svetliakov] extension - which imho is superior to 'VSCodeVim' ... in combination with the 'Which Key' [from VScpaceCode] and 'harpoon' VSCode extensinos its almost the full monty
As a noob I have felt like go is the hardest language to google because of all the false positives with the word "go" and "golang" or "go lang" might filter out actual Go resources.
For anyone following Melkey, some tweaks are needed to deploy using newer aws runtime. You need to build your go source and name it "bootstrap" then need to zip it. Careful when you compile your go source, it needs to be linux compatible : I use GOOS=linux GOARCH=arm64 go build -o bootstrap main.go. In the typescript file Change handler propery to "bootstrap", Change runtime to lambda.Runtime.PROVIDED_AL2023, Point fromAsset directly to your zip file, Add architecture property to match what you choose for example lambda.Architecture.ARM_64 Anyway thanks Melkey for your channel.
If junior devs choose a specific language just to have slightly better job opportunities, they are are completely wrong and end up in the Java shit hole. I highly recommend to do and go with what you like, what is modern and/or has great future opportunities.
Amazing CLI tool. Thanks for building this. I’m using the tool to structure a project in production. Although I did had some trouble with DBTX and pgx.pool. Somehow figured things out. Maybe you could also add an option to connect with sqlc as well.
