Thanks for the presentation, "With DDD the idea is take what you understand and make something, and then get some feedback, expand on it, collaborate.. rather than getting paralyzed by trying to get it perfect." @45:24
I would love to hear DDD discussed relative to the context of implementing a or integrating with a SaaS offering. In that case, you have a distinctly more complex situation. You've got business users who understand their business, and you've got a product suite produced by some third party that has *its own* ideas for how to represent the business. In the case of integration work you have yet *another* complexity in that you're trying to bring together business concepts as understood by a business partner, business concepts as understood by a SaaS vendor, and then technical integration work that may not be tied to either of the previous two.
@@JSANL Isn't anticorruption more so that different areas who talk differently about a subject (which adds some value somehow) can keep talking that way (basically explicit translation)? That's not exactly the same is it? In this case you've INTENTIONALLY ceded some topics (like customer) to a SaaS vendor. The implication is that you have CHOSEN to eliminate your local definitions of those topics (otherwise, why invest in a CRM or ERP for example -- their PURPOSE is to manage certain topics, no?)
The situation you describe where you are integrating with another 3rd party bounded context can add a lot of complexity. There's the technical integration, which can be challenging enough. I would also recommend explicit translation and isolation (e.g. anti-corruption layer) from the 3rd party SaaS offering. SaaS offerings tend to cover generic subdomains, so you can write supporting subdomain code to isolate yourself from them, and thus protect your contexts from the 3rd party concepts. It is tricky though, because these SaaS offerings (e.g. Salesforce, SAP, Contently, etc.) cover a lot of ground and entire sections of the business may "live" inside the SaaS.
@@Calphool222 I think about anticorruption the same way generally. An example might be an organization that manages CRM inside of Salesforce, but still needs to bring in that contact/customer information into their own contexts and use their own terminology and business rules to manage it. For example, maybe they are managing passengers for flight bookings, and so should be using that language in their own context for all the rules around bookings, fares, and discounts for passengers, though all the email interactions with passengers could be managed inside of Salesforce. This is just one simplified example, but hope it helps.
From the title I was expecting the speaker to take a particular example, and talk about how the situation unfolds from an early stage mess through stepwise refinement towards a well architected solution and how that solves the original painpoint the enterprise experienced - instead this talk goes all over the place, reminds be very well of preseidenctional debates of these days - lots of talk, no concrete policy.
Thank you so much for this great presentation. I am java developer. I browsed lot of tutorials to get understanding of DDD but couldn't not relate that information with the product I build. Today I got the fair idea on DDD.
Thanks for the feedback. I'm not sure what kind of example you might be looking for. If it's a coding example, then maybe this talk th-cam.com/video/o_vAjX2vHu8/w-d-xo.html would be more useful for you.
Finally a presentation about DDD with concrete examples, without all the typical mumbo jumbo. Thanks so much!
You're welcome! Thanks.
Thanks for the presentation,
"With DDD the idea is take what you understand and make something, and then get some feedback, expand on it, collaborate.. rather than getting paralyzed by trying to get it perfect." @45:24
You're welcome. Glad it was helpful.
After extensive research, this video turned out to be more easy to understand and relevant.
Thanks.
I didnt know Steve Nash is a DDD advocate
You're not the first person to mention I look like Steve Nash. LOL :)
Thanks! clearly and deeply
Glad to hear it!
Thanks a lot for this talk, as a DDD beginner this was very useful and relatable.
Thanks. We're all learning.
Great video - thanks!
Thanks for the feedback
I would love to hear DDD discussed relative to the context of implementing a or integrating with a SaaS offering. In that case, you have a distinctly more complex situation. You've got business users who understand their business, and you've got a product suite produced by some third party that has *its own* ideas for how to represent the business. In the case of integration work you have yet *another* complexity in that you're trying to bring together business concepts as understood by a business partner, business concepts as understood by a SaaS vendor, and then technical integration work that may not be tied to either of the previous two.
I think thats what an anti-corruption layer is typically used for.
@@JSANL
Isn't anticorruption more so that different areas who talk differently about a subject (which adds some value somehow) can keep talking that way (basically explicit translation)? That's not exactly the same is it? In this case you've INTENTIONALLY ceded some topics (like customer) to a SaaS vendor. The implication is that you have CHOSEN to eliminate your local definitions of those topics (otherwise, why invest in a CRM or ERP for example -- their PURPOSE is to manage certain topics, no?)
The situation you describe where you are integrating with another 3rd party bounded context can add a lot of complexity. There's the technical integration, which can be challenging enough. I would also recommend explicit translation and isolation (e.g. anti-corruption layer) from the 3rd party SaaS offering. SaaS offerings tend to cover generic subdomains, so you can write supporting subdomain code to isolate yourself from them, and thus protect your contexts from the 3rd party concepts. It is tricky though, because these SaaS offerings (e.g. Salesforce, SAP, Contently, etc.) cover a lot of ground and entire sections of the business may "live" inside the SaaS.
@@Calphool222 I think about anticorruption the same way generally. An example might be an organization that manages CRM inside of Salesforce, but still needs to bring in that contact/customer information into their own contexts and use their own terminology and business rules to manage it. For example, maybe they are managing passengers for flight bookings, and so should be using that language in their own context for all the rules around bookings, fares, and discounts for passengers, though all the email interactions with passengers could be managed inside of Salesforce. This is just one simplified example, but hope it helps.
From the title I was expecting the speaker to take a particular example, and talk about how the situation unfolds from an early stage mess through stepwise refinement towards a well architected solution and how that solves the original painpoint the enterprise experienced - instead this talk goes all over the place, reminds be very well of preseidenctional debates of these days - lots of talk, no concrete policy.
Thanks for taking the time to leave feedback
Thank you so much for this great presentation. I am java developer. I browsed lot of tutorials to get understanding of DDD but couldn't not relate that information with the product I build. Today I got the fair idea on DDD.
Glad to hear it was helpful. Thanks!
There is no example, how disappointing (
Thanks for the feedback. I'm not sure what kind of example you might be looking for. If it's a coding example, then maybe this talk th-cam.com/video/o_vAjX2vHu8/w-d-xo.html would be more useful for you.
« By example » LOL !
Show us code !! This is pure theory !! Not real life !
Thanks for the feedback. If it's a coding example, then maybe this talk th-cam.com/video/o_vAjX2vHu8/w-d-xo.html would be more useful for you.
Sounds like a rant than anything useful. Sorry buddy!
Thanks for watching and thanks for the feedback.
Get to the point... ranting more than giving useful information.
Thanks for the feedback.
@111aaqq