Відео

wow : ) Looks clean!

Where is the code snippet? You have shared your whole GitHub

Isn't emitting an event before knowing that persistence was successful a bit premature? What happens if the service goes down before the user is stored, but another service consumed your event? I usually use my data layer (be it pg, or some other store) to set the fields like id, or the timestamp fields, then queue from the store to emit. Btw, great video. We need more hands on Go content!

I've been learning Go as one of my goals in 2024, and unfortunately haven't had too many opportunities to use it because I've been working as a front-end engineer for two years (hopefully I can go back to backend next year), but this really helped me understand the usability of go routines! I already thought of a use case for it in my own application. I have an app that has one endpoint which stores purchase information from a mobile app (electronic cash register, ECR), to the database, and from the ECRs perspective it doesn't matter if that operation succeeds or fails; they've already made sure the money has been collected before it sends in that request to store the purchase information. Anyway, long story short, I had to set up a queue to make that whole thing asynchronous and faster for the ECR, so that it doesn't have to wait for the operation to finish, but goroutines would've probably saved me that headache. Too bad I wrote it in TypeScript. And finally, thanks for this short video!

hey man it would have been cooler if one can see the github repo for this application trying to get an overview of how you structured you application.

I didn't think of using hx-swap=#{{$id}}. That's so powerful. RIP JS ( even though htmx is js, we don't have to write as much js, if any at all )

Why would we be using txn if we follow this pattern ?

If incrementing the view count fails you will end up with an inconsistency, the request that should have failed will be interpreted as succesfull...

how do you handle db transaction in service pattern? like using 2 separate services in the handler function.

What’s your thoughts on using DTOs and newing up domain models in the service vs newing up in the adapters and parsing domain objects to services? I’ve seen both approaches and see pros and cons for both as well. What do you think about creating ports for the services as well? So the driving adapters are not depending directly on the services, but of a port of the service?

Bro I am new to go just wanted to know is it h exagonal architecture?

6:55 I think you meant to name it GetUser instead

but the fields should be private in the Domain layer

What does this look like when you start to have 10, 20, 30 repos and services? How can you organize them with this pattern in mind? Are all of the services and repos created in main, and passed down through closures?

Bruv 5 months no upload

This is good stuff. I dont see any example code your github that references this pattern, where can i see that? Thanks

I see your interface has return pointer to local *Profile. How does storage / postgres satisfy this? doesn't it introduce circular dependency if postgres is returning *customer.Profile?

a good video , great value

I thought you would show a rate limit by IP address to this endpoint, you're only adding it to the cache

which font is this

you're an superstart bro😃😃

really useful thanks mate

4:10 You might find NATS interesting as an event broker. Since it's written in Go, you can even include the server it in your app and scale out to global levels later. ;)

Good ❤❤❤

Your teaching style is good keep up the good work.

You don't need the log level map to convert string to log level as slog.Level implements UnmarshalText. You can use flag.TextVar(&opts.logger.level, ...) instead of flag.StringVar and it'll happen automatically (go run ./main.go -log-level debug).

Do you think it is possible to create a UI component library that works alongside a CLI to generate static HTML files? I was searching for a good method to accomplish that.

I guess I have to get frustrated with life without templ to feel motivated to try it

Yeah, TEMPL seems a bit too much. I just want my tailwind in my go. I don't know what all the other stuff is. Does someone feel me on this?

Ah, I have used this pattern without knowing this is what Dependency Injection is. Thanks for this video.

Thanks for a very pragmatic example

So much code and you are still going to end up with thousand lines of "if err != nill" When people are asking for better error handling I am not sure that we worry about how to transfer error details, but rather how to make the code cleaner and less repetitive.

If the errs.Set method would deal with the second parameter "err" and would set the error only if it is not null, we could save a lot if "if err != nil {}", and email, err := input.Email() errs.Set("email", err) would be enough. Just an idea. Code readability may be compromised.

good content, tnx, but why background music??? it is hard to understand

Thanks for nice video and sharing your experience. your content is more advance. I found one more vdo on how to handle panic error, may be it will help others ua-cam.com/video/I64eE3OyEW0/v-deo.html sharing is caring.

Should domain service method params be passed as already validated domain objects or should they be provided as primitive types (like in this video)?

Yes, I learned

Which theme are you using

What of fiber rate limiter middleware

What is the benefit of this ?, if want help ppl learn golang show them how u start this project from scratch :)

noob question. Writing html element in a text file gives output to a browser. Why do we need a extra html template engine again? i could not get the whole functionality.

programming font name?

Since you have an invalid field, why should we waste cloud processing (seconds = $) to validate others? It looks nice, but it doesn't feel usable.

You just explained the general concept of DI, there was nothing specific to Go. The hard hard is, how do you register dependencies and create a system that automatically injects the correct dependency. Sorry but you missed the point.

What linter do you use?

Great video and thank you for describing where in real time one can see such usage. You got me subscribed and thumbs-up!

'promo sm'

Thanks Sam! I am doing a huge research and learning more how to do a template or a basic structure to use in the project and is very hard as you know everyone do a different kind of organization. DDD, Clean Arch, Hex, DDD + Clean , omg! So, do you have some repo that represent this kind of structure that you are using? I like the *types that you use but not get so much how do you deal with the services and bus types. Do you have one service for each entity of your bus logic? Not sure if I separate the service from the type. Tks a lot! If you have any recommendation of project template or even a course that I can watch, do, see, search I will really appreciate. And thank you for your videos, they are an inspiration for me. Do you work as a freelancer?

Damn, this is nice. Imho it would be perfect if you finish it off with some dependency injection, specific error handler interface which is later on implemented by a few packages, http, grpc... So then when you switch from httperror to grpcerror you do it in one place by replacing the structure instead of refering to a different package everywhere :)

Had been reading a lot about contexts and goroutines but this video made a lightbulb go off in my head. The real world examples really help, thank you for that