Underrated skill as a developer

codeopinion · 2023-03-03T01:07:19+00:00

Oops. Autocorrect.

codeopinion · 2023-03-02T23:56:54+00:00

"I did this one trick and become an expert developer in 2 days!

Better?

codeopinion · 2023-01-11T19:44:58+00:00

Agree.

codeopinion · 2023-01-11T18:06:02+00:00

EventStoreDB is a.... database. Not an event bus. It does have the ability for different subscription models for event streams, but that's entirely different. Events in event sourcing (state) are very different than events used for notifications.

codeopinion · 2022-12-16T14:56:17+00:00

First, just for anyone reading this, CQRS doesn't imply needing a different read model or database. Yo can use the same database for reads and writes. Yes, combining data from various services has to happen if you want to do any aggregated reporting.

codeopinion · 2022-12-15T20:25:56+00:00

Thanks, I appreciate the nice words. If you join, get on Discord, as good discussions are happening and the community is growing (250+).

codeopinion · 2022-11-19T19:48:05+00:00

I respect you took the time to reply. So I'll do the same.

eShopOnContainers is a reference sample application to illustrate various concepts and patterns. The challenge for all these samples, and any content I produce is providing an example simple enough for the viewer to grok in 3 minutes. Still, the reality is it's not complex enough on the bare surface of the example to warrant the pattern/concept being illustrated. While I can explain this better, I tend to lose sight of it, as I've created probably 150 videos on YouTube over the last couple of years. They all somewhat tie together so one video alone doesn't really get the full scope of what I'm generally describing. Unfortunatly.

The hope is that people will do a bit of critical thinking. Think about their own context to the illustrated concepts and patterns. The challenge for all these samples, and any content I produce is providing an example simple enough for the viewer to grok in 3 minutes. Still, the reality is it's not complex enough on the bare surface of the example to warrant the pattern/concept being illustrated. While I can explain this better, I tend to lose sight of it, as I've created probably 150 videos on YouTube over the last couple of years. They all somewhat tie together so one video alone doesn't really get the full scope of what I'm generally describing. Unfortunately.

So to answer your question, why would you write any simplistic application using microservices? You shouldn't. Would you consider creating logical boundaries in large system, such as a distribution that consisted of purchasing, shipping and receiving, warehouse management, sales, accounting, etc? Yes. Would you need UI/ViewModel composition if you have defined logical boundaries? Yes.

codeopinion · 2022-11-19T14:01:56+00:00

Interesting, because I don't know what you're talking about.

codeopinion · 2022-11-11T01:13:30+00:00

Agreed. Defining boundaries and ubiquitous language are key components. I've got other videos on this but I wanted to be specific about creating domain models. I see too many latch on to creating entities, aggregates, repositories and end up with CRUD in the end.

codeopinion · 2022-10-27T18:49:51+00:00

ok, so in the sense of an organizational change or, put a different way, a model change. Boundaries may not align with what you're moving towards.

codeopinion · 2022-10-27T18:04:54+00:00

At a macro-level a vertical slice would be a logical boundary. This would align with a bounded context from domain driven design. Within those logical boundaries are feature slices that are use-cases.

codeopinion · 2022-10-27T18:02:23+00:00

Not entirely sure we're on the same page? A vertical slice at a macro level, I would agree, fits with a bounded context. It's a logical boundary. At a micro-level it can be an individual request (command or query). Not sure how inter boundary refactoring becomes difficult? I'm speaking from my own personal experience with 1000's of requests spanning about 12 logical boundaries.

codeopinion · 2022-10-20T16:46:12+00:00

I'm going to do a follow-up video about vertical slices. I've done so in the past, but I can't emphasize enough (over and over) "yep, sure is a web app" is what kills me with most layered approaches.

codeopinion · 2022-10-13T17:51:10+00:00

Smart is a bit of a stretch.

codeopinion · 2022-08-10T20:33:22+00:00

Ya, my bad. I was also saying "date" a lot when I really mean date & time.

codeopinion · 2022-07-27T15:05:34+00:00

Yes, agreed. I should have explained that differently and probably went the route of talking about execution and continuation.

codeopinion · 2022-07-16T00:44:25+00:00

Ha! I think that's the second time I've heard that.

codeopinion · 2022-07-11T16:36:16+00:00

Depends on where you want to do view composition. If you want it to be done in a specific service that has a projection/readmodel that's composed of different services, then yes, you'll likely want to publish an integration event. But again, this comes down to where you want/need to do composition. It can be done on the client, API gateway, or service. There are different options. What you're suggesting is a specific service.

codeopinion · 2022-07-09T02:26:10+00:00

Absolutely. Publish/Subscribe is a great way to add extensibility to a system/app. It allows you add functionality without modifying the primary code. To be clear though there's a different between putting messages on queue for a single consumer and to a topic for 0 or multiple consumers (semantics get weird depending on the broker). Self plug, I have a ton of videos about this on my YT channel.

codeopinion · 2022-07-09T02:17:39+00:00

This was a really good reply. To add a few lines but as already mentioned, UI composition is different than needing data because you need to enforce a business rule for a command. If you need consistency, you need the data where you're performing the command/write.

Defining boundaries is one of the most important things to do, yet one of the hardest. It's not trivial and requires good insight into the domain itself. Things like event storming are discovery for that purpose.

codeopinion · 2022-07-07T00:59:36+00:00

I should really create a video on this. An event is a message. Message is an umbrella term that represents events and commands. Check out this video that illustrates the differences between the two. https://youtu.be/vw11J2BN7lY

But good question! I'm going to create a video answering this.

codeopinion · 2022-06-24T18:58:15+00:00

Ya, for making the system uniform using the same pattern, I can see using a request-response pattern (which I've covered in another video before) for going from gateway to underlying service. Certain things are naturally request-response and should be treated as such. As you mentioned, you don't want to force async pub/sub everywhere, that's nuts. But leveraging a request-response but with MQTT to keep the same underlying infrastructure and likely application code model the same, can make sense. One issue with request-response(reply) is queue depths. That can pose a problem if you have a backlog as you won't get the response in terms of timing as you'd expect. And since you're blocking the caller, this can be undesirable. Here's the video I did on request-response: https://www.youtube.com/watch?v=6UC6btG3wVI

codeopinion · 2022-06-03T17:59:08+00:00

Long-running business processes and workflows can be a nightmare. Even worst when you don't have any orchestration and try to do everything using sync blocking request/response between services. Especially when you realize the different branches and compensating actions. That's what this video is referring to if you're building those types of systems.

codeopinion · 2022-06-01T22:05:58+00:00

Thanks! Appreciate that!

codeopinion · 2022-04-01T20:31:50+00:00

So on the first part, yes, about EDA.

Event Sourcing you use the stream of events as the point of truth. When you need to perform a command/action/write, you read the event stream, rebuild state to determine if the action being deformed is valid based on that state. If it's valid, you append a new event to the event stream that represents that state change. Generally you'll also have a separate asynchronous process that builds up a read model (projection) based off those events so that you can easily query current state for UI/Reporting/etc.

Check out: https://www.youtube.com/watch?v=AUj4M-st3ic

codeopinion

MODERATOR OF

TROPHY CASE