ESN 6467008030256383535

Rate Content: 1 vs Document Name: SOA Bootcamp - Wrapup Document Description: ONE STEP AT A TIME. JUST LIKE ESTABLISHING AN EA PROGRAM FROM THE FIRST TIME, YOU NEED TO START SMALL, ITERATE, MAKE ADJUSTMENTS, AND MOVE ON TO THE NEXT CHALLENGE. IMPLEMENTING SOA IS A LONG JOURNEY. DON'T TRY TO DO IT ALL AT ONCE! ABSTRACTION IS THE KEY. YOUR SERVICES SHOULD BE VENDOR INDEPENDENT (EX: SHOULD RUN ON ANY ESB WITHOUT CHANGES TO THE SERVICE), BUSINESS PROCESS INDEPENDENT, DATABASE INDEPENDENT, ETC. IF THIS IS NOT THE CASE, THEN YOU ARE NOT DOING SOA. MOST LIKELY, YOU ARE DOING ABOS (A BUNCH OF SERVICES). THE "TIPPING POINT" - IF YOU DO SOA RIGHT, YOU WILL REACH A POINT WHERE YOU SHIFT FROM CREATING SERVICES TO CONSUMING SERVICES. WHEN YOU FIND THAT YOU ARE SPENDING MOST OF YOUR TIME ASSEMBLING SOBAS (SERVICE ORIENTED BUSINESS APPLICATIONS) THEN YOU KNOW YOU HAVE ACHIEVED SOA. LET THE LEGO BUILDING BEGIN! START WITH A PILOT. DON'T FORGET THAT GOVERNANCE AND ARCHITECTURE SHOULD BE PILOTED AS WELL. DON'T JUST PILOT SERVICES. IT TAKES SERVICES, GOVERNANCE, AND ARCHITECTURE TO CREATE SOA SO DON'T LEAVE ANY OF THESE OUT OF YOUR PILOT. DESIGN TIME GOVERNANCE - ENSURE THAT TEAM MEMBERS ARE FOLLOWING BEST PRACTICES THAT APPLY TO SERVICES. GOVERNANCE SHOULD NOT BE A BURDEN AND A TON OF PAPER WORK. IT SHOULD BE VALUE ADD AND HELP THE TEAM BUILD A TRUE SERVICE ORIENTED ARCHITECTURE. DESIGN TIME ISSUES INCLUDE VERSIONING, METADATA MANAGEMENT, POLICY MANAGEMENT. RUN TIME GOVERNANCE - ENFORCE AND MONITOR RUN TIME POLICIES AND SLAS. SERVICE DEVELOPMENT DOESN'T STOP WHEN A SERVICE IS DEPLOYED. THE SERVICE LIFECYCLE CONTINUES THROUGH RUN TIME. WE MUST PLAN FOR ONGOING CHANGE OF SERVICES. RUN TIME ISSUES INCLUDE SERVICE AVAILABILITY, POLICY ENFORCEMENT, SLAS, CONTROLLING TOTAL COST OF OWNERSHIP (TCO). DON'T TEST THE ARCHITECTURE - TEST THE INDIVIDUAL COMPONENTS AND HOW THEY INTEGRATE TOGETHER. DIVIDE ARCHITECTURE INTO DOMAINS AND VERIFY THE DOMAINS. THINGS YOU NEED TO TEST: SERVICES, SECURITY, BUSINESS PROCESSES, INTEGRATION, AND ALSO THE GOVERNANCE. SERVICES SHOULD RUN WITHOUT DEPENDENCIES. TEST SERVICES ACROSS MULTIPLE PLATFORMS AND TEST FOR ABSTRACTION. FUNDING AND THE BUSINESS CASE - DON'T TALK ABOUT THE TECHNOLOGY, TALK ABOUT THE BUSINESS PROBLEM! HERE IS SOA PITFALLS - DON'T LET THE VENDORS OR CONSULTANTS DRIVE YOUR ARCHITECTURE. CREATE VERSIONING POLICIES. WITHOUT THESE YOU MAY NOT ACHIEVE LOOSE COUPLING BECAUSE YOU MIGHT BREAK THE CONTRACT YOUR SERVICES HAVE WITH THEIR CONSUMERS. ORGANIZATIONAL CHALLENGES - HERE IS THE BIGGEST CHALLENGE OF THEM ALL. YOU CAN ALWAYS FIND A BUNCH OF SMART PEOPLE WHO CAN FIGURE OUT THE TRUE MEANING OF BEING SERVICE ORIENTED. BUT HOW CAN YOU MAKE PEOPLE CHANGE? REMEMBER THE DAYS OF TRYING TO GET MAINFRAME DEVELOPERS TO ADOPT CLIENT SERVER? GET READY TO LIVE THOSE DAYS AGAIN. SINCE SOA BLURS THE LINES BETWEEN APPLICATIONS, MIDDLE MANAGERS MAY LOOK AT SOA AS A THREAT. TYPICALLY, THE ARCHITECTS DO NOT HAVE THE ENFORCEMENT POWER/AUTHORITY NEEDED TO ENFORCE BEST PRACTICES. THIS IS A MAJOR CHALLENGE WITH SOA. STILL MATURING - SOA BEST PRACTICES ARE VERY DYNAMIC. THIS TECHNOLOGY IS STILL MATURING AND THE VENDOR TOOLS AND STANDARDS ARE STILL EVOLVING. WHAT'S NEXT?Author: Michael Kavis - Contact Author Publisher: Michael Kavis Licensee Name: Michael Kavis Reference URL: http://blogs.ittoolbox.com/eai/madgreek/archives/soa-bootcamp-wrapup-22839 Copyright: All Rights Reserved Registration Date: 3/3/2008 4:24:42 AM UTC Views: 540

NUMLY.COM