vault backup: 2024-08-08 15:47:33

2024-08-08 15:47:33 -05:00
parent 59d0938651
commit dc590594d2
492 changed files with 104 additions and 72 deletions
--- a/Training/Advanced
+++ b/Training/Advanced
@@ -0,0 +1 @@
+How to communicate back to the organization?  This is especially when the organization is already using SOA terms (like service) for other things (like REST or WCF services).  You can slowly introduce SOA by using new terms (bounded context, business capability, etc) that are basically the same things that SOA talks about but are different to the organization and help get everyone thinking in a different way.   If I have two things that I'm not sure about splitting up or combining together, will I be better off combining them or splitting them?  When we come across a situation like this, it's often an indicator that we are slicing up the boundaries incorrectly.  We need to think of everything in 3D terms, looking for the right angle to slice the pieces where the boundaries make most sense.  When trying to find the boundaries, it's usually the case that we are totally confused as we look at how to split everything up (find the boundaries) until we find the right angle and then everything has a certain obviousness to it.  Every industry has it's own angle of attack to decompose the elements of the business into service.  If we figure it out in one industry, that same angle won't necessarily work in another industry.
				`@@ -0,0 +1 @@`
				How to communicate back to the organization? This is especially when the organization is already using SOA terms (like service) for other things (like REST or WCF services). You can slowly introduce SOA by using new terms (bounded context, business capability, etc) that are basically the same things that SOA talks about but are different to the organization and help get everyone thinking in a different way. If I have two things that I'm not sure about splitting up or combining together, will I be better off combining them or splitting them? When we come across a situation like this, it's often an indicator that we are slicing up the boundaries incorrectly. We need to think of everything in 3D terms, looking for the right angle to slice the pieces where the boundaries make most sense. When trying to find the boundaries, it's usually the case that we are totally confused as we look at how to split everything up (find the boundaries) until we find the right angle and then everything has a certain obviousness to it. Every industry has it's own angle of attack to decompose the elements of the business into service. If we figure it out in one industry, that same angle won't necessarily work in another industry.