@dmitry.gashko
4:40 we dont have to use packages for fetch, but what its still a better to do - is to wrap the native fetch with our own fanction. E.g. makeApiRequest. So, is nicer no use, and if you need to change something globally - you can do that. E g. Add common headers, etc
@Kogo180
hey taijo you are uploading awesome content on go can you make complete playlist on go from basic to advance level a complete playlist that will be very helpful for all people building small small project to large scale projects it will be very helpful if you can do
@ikraamdev
If Go had the equivalent of drizzle-orm and better-auth, maybe Iād use it lol the TypeScript ecosystem is just too simple to not use.
@quamzgraphix9826
I am using the same stack to build one of my personal projects
@Alnzbar-m8v
Much better with mic
@s1dev
can you make a guide on deploying a nextjs + golang project maybe dockized + ci/cd and some kinde of db? what do you use?
@soumyadeepghosh4428
Man can you please release a full stack course using react/next + go( for backend )? I'm so much f up with node & express. Also can you please release the course on udemy? I am not able to get a subscription on your website due to some card related issues:(
@AzmineIktidar
In the next.js server actions, you have full type safety during calling those functions. How do you address that when using the fetch method?
@prashlovessamosa
try blueprint golang its quite good
@mrudulmohan9219
can you please do a tutorial with another aaplication having same tech stack
@rishabhtiwari976
microservices with go on Udemy when?
@brunonovais8801
With nextjs instead of one backend now you have 2
@Qubit-sj6qo
Greetings Tiago, I am bacc with another doubt - I am working on a notification system project using NATS JetStream and have a silly doubt. So I have a gateway service that communicates with an event store service by gRPC. The event store is responsible for publishing notif into a stream. The notifications come from different applications and have different types While publishing, I am building the subject on fly like this: <appName>.<notificationType>.<event>Now I am confused on how to properly structure the subscribers. Should they subscribe to specific subjects (how will they know the specific subject), or should I use wildcards? If I use wildcards, how can I classify each notification type? My goal - I want to send notifications separately to members, admins, and leads from my HR applicaton, same for ERP application and so on. Would like some guidance on this approach.Lmk if you need more details or if there's anything off with my design
@prashlovessamosa
tiago you havent updated the udemy course frontend part is still missing.
@NitinUpadhyay-p6q
I would appreciate it if you could add the Hindi language.ššš
@GeovaneGC
what vscode theme is this?
@jcolindres001
Hello Tiago, How do you deploy the backend project (in Golang)? Regards,
@pawel_890
You can be much faster with backend with Nodejs, is has near same performance and you can ommit Go complexity for simple saas
@sbasu31ag
How are you deploying the backend?
@Noeeekr