Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    That is what the term event based system would make sense for, to trigger sequences of dependend actions to another, independent parts of the system, avoiding time lags and polling this. This paragraph summarise why there's no need of EDD. IMO. Commented Jul 2, 2017 at 17:37
  • @DocBrown, perhaps there's indeed a confusion. I'm thinking about events as in domain events from DDD, which AFAIK is a way to record that relevant business happenings have occured. The report will certainly not be immediately generated. What the customer wants is that employees inform when they start working on a project on a day and when they finish it, to have this information. He says it's like when the employee clocks in when he arrives and clocks out when he leaves. Perhaps I misunderstood domain events. Commented Jul 2, 2017 at 17:59
  • I think by "event-based system", OP is talking about event sourcing. Unfortunately the confusing terminology may have mucked the question up a bit since now it has answers like this one that are partially based on it, and that innappropriate "event-programming" tag. Commented Jul 3, 2017 at 12:17
  • @BenAaronson: I think one can interpret the question as: is "event sourcing" or "event programming" is the right tool for handling this kind of "events" (=logging of working hours)? My answer: it is not necessary, it probably overcomplicates things, and by designing the logging table correctly, the problems described by the OP can all be solved. Commented Jul 3, 2017 at 13:27
  • 1
    @DocBrown Fair enough. I think your tuples suggestion is actually very similar to what the OP was describing, but you're right to emphasise it can be as simple as that without a full-blown, heavyweight event sourcing architecture Commented Jul 3, 2017 at 17:15