Ask questions and see you on November 3 at 8pm CET: youtube.com/c/bienadam
Also check out the latest episode:
Please keep the questions as short and as concise as only possible. Feel free to ask multiple, shorter questions. I will also answer some questions in my "shorts" youtube.com/@bienadam/shorts between the shows.
Upcoming airhacks.tv events will also be announced at meetup.com/airhacks
New: The airhacks.tv discord server: discord.gg/airhacks
In your BCE design, in the Example: User Management, you have...
boundary - REST endpoints, Custom Elements, Lambda function handlers
Can you give an example of a Lambda Function Handlers? (Are we talking about AWS here?)
Can you also define what counts as a Custom Element? Are we talking about objects that are part of the business domain but don't fit within the Entity package? For example, if we are having a BCE for buying a plane ticket, would the data in a search form to find a flight be an example of a Custom Element?
In the bce pattern, where do you place the global exception handling code? eg if I have booking and payment packages and I need to handle exception thrown in a central place(maybe switch(ex) return to user what happened), where will all these be?
This one is about entities and dtos. The usual talk I have heard is entity classes should not be used to transfer data we should use dtos. Eg if we are having an entity User, in the create user resource we should use like UserRequest dto, then map to user afterwards. Is this cargo cult or are there any valid reasons as to why most people say this? I have seen this in spring boot alot.