Get flash to fully experience Pearltrees
There is a frequently recurring piece of software development lore that plays on the fact that good programmers are supposed to be lazy . In these stories, a good programmer will take a frequently recurring, monotonous task (like testing) and instead of doing it by hand, will instead write a piece of code once that will do the task for them, thereby automating it for future use. Put another way, instead of carrying out the work by hand, a lazy programmer will spend 95% of the time allotted to the work by developing code that will carry it out for them, and the last 5% of the time will be spent running it to get the actual work done. Then, every time the task must be carried out in the future, software can be directed to complete it swiftly and automatically.
In many customer engagements, I need to establish a basic set of SOA principles. The following sections introduce fundamental principles that a Service Oriented Architecture (SOA) should expose. They are not introduced as absolute truth, but rather as a frame of reference for SOA-related discussion. You'll note that the first four are based on Don Box's four tenets, although over time they may have acquired a personal spin. 1) Explicit Boundaries Everything needed by the service to provide its functionality should be passed to it when it's invoked.