In my example, I don’t see the need to have a full replica of Product data set, I would only share the identifier of the product.
The Shipping Service would subscribe to the ProductCreated event, but it would use it to save its “defaults/rules” to save the Product.
First of all thank you for taking the time to comment. Very appreciated.
After reading the article you pointed out, I have found the same basic message in both mine and yours. Communication is key.
What’s the least we can draw or model to communicate the intent? Often, the feedback on drawings from…
I couldn’t agree with you more. Data is an important and yet normally ignored aspect of software engineering field. Without data we are only guessing.
I think we, engineers, don’t like it very often, because of our history with management and KPI based on wrong things — but there is a topic for another article maybe :).
The junior may have the perfect solution, it was an example to make the point.
There will be decisions the team can and should make, but we should not confuse autonomy with freedom to choose whatever the team wants.
Hi Tiago, Thanks!
I agree with you and the solution will be better and better with the feedbacks we have during the process. There will be some assumptions that will be validated during spikes or somewhere in the future. Those can be done by software engineers, software architect or whoever has the time for it. The main goal…
Thanks! And thanks for sharing the SCS link, I didn’t know that. Some thoughts on it: