SDA India is an online resource for Software, Development,IT, Architecture, Open Source, Mobile, Security, Databases, Delphi, C, OS, Asp, .Net, Php, Xml, Java
Planet SDA-India
I dragged myself to Redmond last night to attend Microsoft’s Fifth annual SOA and Business Process Management (BMP) conference. First, Microsoft states that it will not be designing and announcing its own enterprise service bus but will in fact allow customers to leverage whatever service bus(s) they already have. This sounds the same as HP’s philosphy towards ESBs. Second, the world of technology is based on a federated model (I agree). Given this philosophy, Microsoft is now talking about the Internet Service Bus — a publish/subscribe model for interoperability that leverages existing middleware. This is being offered as part of BizTalk Server and is being offered as a hosted cloud service by Microsoft. Third, Microsoft is making two big bets: a service orientation to creating applications by expanding and exploiting existing technology and providing hosted services via a set of cloud services that act as an integration framework. If customers want, they can move hosted services back to their enterprise. Providing shared models that can go across. Fourth, Microsoft is making its entire plaform model driven that is backed up by a SQlServer based repository. This becomes a general purpose modeling platform with a set of tooling.
Microsoft Announces Major SOA Initiative, And a Whole New Wave of Innovation
Brian Loesgen
| Link to this blogEvery once in a while an announcement happens that has the capacity to profoundly change the rules. I still remember clearly reading the initial press release in 1999 about this new thing from Microsoft called “BizTalk”, and, I remember telling a co-worker that I was going to keep an eye on this new BizTalk thing. Here I am, 8 years later, still deeply immersed in the world of BizTalk. I would rate Microsoft’s Oslo announcement today as being equally important. It is an ambitious undertaking, one that changes the rules for .NET developers. For me, this is déjà vue all-over-again with that 1999 press release, with the significant difference that this is an evolutionary change, and the reach will be far greater, touching most .NET developers.
For a system administrator who works with computers in the data center all day there are at least two areas where you can help daily: data center electricity use, and paper use. The data center is becoming responsible for an ever increasing amount of electricity use, and generators are already maxed out in many locations in the country. Reducing electricity usage in the data center will not only reduce the need for electricity, it can also reduce your corporate electric bill. Paper, while being a renewable resource, is taking its toll on the trees that exist on our planet (along with the need for lumber world-wide). The biggest problem is that trees are being consumed faster than they can be regenerated - trees take many years to grow, and only minutes to take down.
My definition of Business Service Management (“BSM”) is derived from my recent experience as the Global CTO for one of the largest private equity companies. In this role, I continually saw that each of our seven + data centers, as well as, in the IT operations of most of our portfolio companies the proliferation of siloed point solutions each covering two or less of the elements of a critical service. For example: In one of our Asian data centers we had three network management products, eleven host or device-oriented point tools, five network monitoring products and at least five security products. Most of these were either not being actively monitored or they were not adequately performing the function in which they were purchased for. For that matter, three of these items were not even installed (“shelfware”)...
James Taylor reacted to a posting about the importance of good Requirements. He sees process as something else than requirements. And he advocates a clear seperation of the concept of Rule and Requirement. First on the process part vs requirements. I see a process as a specific concept in requirements. It can be requirements towards a business: (1) This is the way I want our people to perform this process (a business requirement) Or it can form part of the requirements to a system (a software requirement) (2) This is the process I want the system to follow when processing claims. Or a mix of course. So, is a process definition a software requirement? Sometimes.
A lot of speculation and considerable confusion surrounds the ITIL Refresh. I feel this is good because discussion promotes understanding. A friend of mine sent me a Computer World article discussing some of these changes, "ITIL Starts Making Sense in v3" which provides a very good perspective on the value of the changes to the ITIL framework. The ideas expressed are excellent and right on target. Another set of insights on each of the books comes from the ITSM International Portal. If you're interested, follow the thread of updates through all the books. I'll not restate what these authors have already expressed.
"Back when I was on the Architecture Committee, the developers never listened to me. But, now that I'm Enterprise Architect, I'll show them. I'll put in so many governance policies that they won't know what hit them. And there's nothing they can do about it - because these rules are good for our company." OK, I exaggerate a bit. I know a lot of great enterprise architects that would never think this way. But, I wanted to illustrate my point: In life, the most effective policies are supported by both carrots and sticks. Speeding on the road? Your insurance company gives you price breaks if you don't get caught, and the government gives you fines if you do. Carrot and stick. So, what does this have to do with SOA governance?...
