It always starts well. At first glance the requirements seem straightforward, and implementation proceeds without hiccups. Then the requirements start to get more complex, and you find yourself in a predicament, introducing technical shortcuts that smell for the sake of delivering the new feature on schedule.
In this talk, we'll analyze what appears to be a straightforward e-commerce shopping cart. We'll then go ahead and add a few more use-cases that make it more complex and see how it can negatively impact the overall design. Finally, we'll focus our attention to the business needs of these requirements and see how it can shed light on the correct approach to designing the feature. Walk away with a new understanding on how to take requirements apart to build the right software.



NDC Conferences
https://www.ndcconferences.com
https://ndccopenhagen.com

Search service, price service, risk service – when you model them as services, you end up with a tangled web of dependencies between them and almost all the other services in your system – a horrible distributed monolith.

There’s a reason for that – they were never meant to be services in the first place. Join Udi for a blast from the past looking at how rules engines can fit in the missing dimension of your Microservice architectures. Things will look very, very different.



NDC Conferences
https://ndcoslo.com
https://ndcconferences.com