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.

5
  • This would be great if the code generation process would be something continuous in time. But it only happens once, the whole codebase is generated based on the input from the user. Commented Apr 25, 2022 at 21:01
  • Didnt fully get what you mean by continuous in time. Once you have the user input raise the event. Note here you can have arguments and properties for that event in which you can pass the user input to the consumers. Commented Apr 25, 2022 at 21:08
  • Also one goal of the event driven architecture is that its a background job that can be done by another host or machinr that shares the same database where the events are stored. If you dont need that you can create a custom service that can run multiple classes in parallel to simulate the architecture Commented Apr 25, 2022 at 21:12
  • After second tough you dont need a custom service if the development or business needs doesnt require this. You can use the parallelism provided by the programming language Commented Apr 25, 2022 at 21:16
  • I wish to build an application that is ran once with a certain combination of configuration parameters and that delivers the whole codebase as an answer. Another generation of could would mean running the application again. This event driven approach would definitely make sense in a distributed application, but that is not the case. Commented Apr 26, 2022 at 7:02