Видео

Great video, love the paradigems

Thank you!

Amazing work explaining it! In the service factories that accept variadic configurations, I think it would be better to accept a connected client instead of a connection string. Reasoning is that you only have a single connection shared by many services (assuming that the database is the same for all the services). I guess you can have another service config func like "WithConnectedMongoClient(conn)" to cover that scenario

Hi! Great video! Any chance you could share the excalidraw?

Great video. What if you want to use this logger in multiple files without creating it again and again? Like create once and use everywhere?

I don't have much time for my interview why was afraid weather I am able to complete kafka or not but this video help me to gain confidence to stick with rabbit MQ for streaming as well

I read it books on event driven architecture and official rabbit MQ website but the level of clarity depth and knowledge the provided by a videos or incompatible thank you so much

I watched your video a few months ago and I didnt understand a thing now after Ive completed my basic books and now when I am leaning towards dev ops your videos are soo helpful to me I cant put in words. But still if i have to say something that is it took a level of skill and knowledge to understand the depth of your videos, I wish i got a change for a 10 min zoom call there is a lot i want to learn from you. Apart from your video your website also as a revision notes for me and both are valuable for interview preparation and overall understanding of the concepts

@programmingpercy Aren't your customer and product domains creating separate connections to the same db ? (can be seen around 1:50:00)

For some reason LinkedIn can’t recognize my og:image if I use relevant link from VSC like “assets/og-image.jpg". It seems like I have to manually turn it into "./assets/og-image.jpg"

hey percy can you please make some stuff on Concurrency Goroutines CPU-Bound vs I/O-Bound Concurrency How to not spawn goroutines in a loop Channels Channel Axioms The Select Statement Go Concurrency Patterns Managing Goroutines Error Handling 1: error channels Error handling 2: result with error Error handling 3: the errgroup package Fan-Out, Fan-In Managing Resources With sync.Pool Initialization with sync.Once Data races Deadlocks Deadlock Detection Deadlock Prevention with Ordered Locks Deadlock Prevention with TryLock Goroutine Leaks please make something on these topics been reading docs but not able to understand.

shouldn't the products field in the aggregate.Customer struct just be []uuid instead of []*entity.Item?

Grest explanation, very beginner friendly 🎉

Such a great video, one thing I noticed is that you some times do "package <packagename>_test" and "package <packagename>" for the test files, is there a reason to add or omit the suffix _test ?

Dang!!! Thank you I hope one day I can get a Golang Job to buy you a coffe <3

Quality content 😍😍

Amazing explanation! Thank you!

I’d buy AnY course you do on Golang Take my money 💵 No seriously make a course on Golang man

thanks bro for sharing this

Sir make a complete series on E-Commerce.

Thanks bro, I learned a lot today

Hey, what font are you using here?

✅ P r o m o S M

You are awesome Percy!!

thanks a lot for such a wonderful video! a lot of useful information, right now we're going to improve our backend architecture (along with migration from Python to Go) and I'm looking for different approaches and experience and feel like you video might help us a lot to build a new architecture.

Nice video man, keep it up ❤

Awesome tutorial! I have one question, your pong/pong handling, from what I can tell its not doing anything if the client stops sending pongs back.

Very Practical Thanks man !!

One of the best videos !!

Fantastic video.🔥🔥

you should make more videos !!!

I have a question about using SSO with self hosted applications. Can I use SSO for Private subnet routing with Cloudflare WARP to Tunnel the same way we do Public hostname routing with cloudflared access?

When i saw testing, i assumed unit testing instead of manually testing. Unit tests would have saved you a lot of time here.

This is a great tutorial, thanks you!

Good work! Thanks… Which tool did you use in this video for graphical schema?

What about generated code (like oapi-codegen)? Then my whole openapi spec is generated into one file. How one should deal with it?

Thanks for the examples.

Question: when wanting to use slog in a ddd project inside the domain objects like entities and agregates, how to streamline the log level for the application ? Domain objects do not depend on outside things so i cannot inject a central slog instance

Thanks for explaining the loop variable "problem" so clearly - have read a lot about it, but your explaination illustrated the underlining Go runtime workings which caused the behaviour.

at 14:50 what you have written permission to Percy.full command? . I am get error.username and password is not allowed

I'm sorry but I'm trying to understand how is for loop + goroutine behavior a bug. What you are doing here is neither bad practice nor a freak behavior. It is behavior that is entirely expected from this code that is by all measures incorrectly written. THIS is the correct code that does exactly what you would expect: ``` names := []string{"Strale", "Caka", "Strahinja"} for _, v := range names { go func(name string) { fmt.Println(name) }(v) } ``` Example shown here (in the video) disregards basic concepts of multi threading that are surely covered on every computer science course on the planet. Now, I'm not trying to be rude and I very much apologize if that is the way I'm coming across. However, considering that there's no actual bug being presented here, how is this update a solution instead of an ability to allow programmers to write code that is, by every possible measure, bad?

Love the way you summarize the new features! Thanks for the hard work

The main reason I was using third party libraries for http was the dynamic paths. Now I don't need to.

Thank you for the video dude !! keep goin

Imho these adjustments in go weren't needed. E.g. the for loop adjustment is simply required or at least it seems due to the fact that the people don't actually know what there doing or how the language works. I'm fine with them but i would the core team to focus on something else

Great video. You explained it very well, I watch every video on this channel with pleasure and care without getting bored. thanks a lot..

Very good video, thanks 🎉

Great video, keep up the good work 😊👍

Even thou you have a point, passing the current name as a parameter to the go routine function pretty much solves the issue

for range on ints is pretty cool too! for example, you can now write benchmarks as: for range b.N { ... }