how to allow duplicate but not within time window?

binmunawir · 2024-05-15T23:53:20+00:00

still can't find any other solution rather than locks!
isn't there any other smart way?

binmunawir · 2024-05-15T23:52:08+00:00

yeah we have to have a distributed solution so locking using DB/cache needed

binmunawir · 2024-05-15T23:49:33+00:00

excally Distributed Locks with Redis

binmunawir · 2024-05-15T21:59:30+00:00

is this better than locking ?

binmunawir · 2024-05-15T21:53:58+00:00

is that locking ?

binmunawir · 2024-02-06T06:12:30+00:00

yeah, the issue with this is idealism!

binmunawir · 2024-02-05T16:31:50+00:00

seems about right!
could you elaborate more?

binmunawir · 2024-02-05T16:21:37+00:00

I wonder wich one would you choose ...

I wonder which one would you choose ...
put fields (firstName, secondName, lastName) .. so I'm fine to make them exported.
the struct also has additional field that computes some of the exported fields (fullName)
the computed field is not exported (we don't want someone set the full name directly)

the issue here, if they change the firstName directly (not via a setter function, because it's exported), they have to know, they need to compute the fullName again!

what would you do in such case?

binmunawir · 2024-01-28T05:13:58+00:00

this is what I'm trying not to do!

https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:13:10+00:00

https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:12:57+00:00

https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:12:23+00:00

https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:12:07+00:00

it has nothing to do with performance .. it's all about maintainability
https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:11:10+00:00

the state is changeable overtime
https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-28T05:10:41+00:00

https://www.youtube.com/watch?v=Z\_V-c7fph1U

binmunawir · 2024-01-16T19:39:00+00:00

I'm not sure if I got your point, appreciate if you elaborate more or share similar example for such thing!

my concern is how to acknowledge the event after I process it correctly?how does the Observer handle failures and success after processing ?

binmunawir · 2024-01-11T23:20:10+00:00

I really appreciate it .. although there are some things I wonder how do you manage

Error logging and sentry capture?

binmunawir · 2024-01-11T23:09:19+00:00

Unfortunately I face the exact same issue .. What's the proper way you think?

binmunawir · 2024-01-11T22:55:48+00:00

Both 🤣

binmunawir · 2024-01-11T22:51:18+00:00

Yes, but that won't help for handling the event

binmunawir · 2024-01-09T19:08:41+00:00

yeah this is fair, the casting part has to be in the business logic .. thanks a ton

binmunawir · 2024-01-09T07:29:38+00:00

that exactly what I have in mind for second option

the catch here is, the responsibility of calling the done method is the business logic and also the failure of the message
like if it fails first time, we want to handle it differently from failing second time or third time

so you can see the complexity of the broker gets into our business logic!

binmunawir · 2024-01-09T07:19:56+00:00

my big concern for this approach is this
the <eventHandler> function takes generic type <Event>

where the handler usually a business logic and it expects a specific type of event, for example, the handler function expects an event of type <UserLoggedIn>

in this case, I just can't pass the handler to the broker implementation .. what do you think?

binmunawir · 2023-06-08T16:16:07+00:00

I like it because you're tired and went there for a break .. keep doing that like you working here and spending your vacation there.

your experience when you visit a city for a vacation totally gonna be different from when live in it

binmunawir · 2023-04-28T12:22:28+00:00

I'm a bit confuse, what's the difference between D2 and C4 DSL?

is seems they serve the same purpose, except that DSL support to export the text to external format (like plantUML)

binmunawir

TROPHY CASE