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 posed a question some time ago asking what the biggest limitation to successful SOA governance was to an organization. As a result I received many interesting response; all of which are likely correct in one shape or another. Finally my response to this question, the article titled Rethinking SOA Governance has been published on the revamped arch2arch site.
And once you've gotten off that airplane, know that we've come up with a new way of making those servers more personally productive as well, and it has nothing to do with to-do lists. Late last week, we announced new virtualization capabilities for service-oriented architectures. The new capabilities for IBM's System p servers help maximize utilization of your existing hardware and software resources by helping centralize tasks, streamline your business processes, and improve your overall system performance. Learn more about these new capabilities here.
One thing that I’ve noticed recently is that there is no standard approach to Enterprise Architecture. Some organizations may have Enterprise Architecture on the organizational chart, other organizations may merely have an architectural committee. One architecture team may be all about strategic planning, while another is all about project architecture. Some EA teams may strictly be an approval body. I think the lack of a consistent approach is an indicator of the relative immaturity of the discipline. While groups like Shared Insights have been putting on Enterprise Architecture conferences for 10 years now, there are still many enterprises that don’t even have an EA team.
Lately, I've been doing a fair amount of work for the newly formed SOA Consortium. The SOA Consortium is a service-oriented architecture (SOA) advocacy group comprised of end users, service providers, and technology vendors, committed to helping Global 1000 enterprises, major government agencies, non-governmental organizations and mid-market businesses successfully adopt SOA by 2010. While I'm still under a gag order for the SOA Executive Summits I facilitated at the end of February, I can share some activity from one of the practitioner working groups. The Enterprise Architecture of the Future Working Group (Enterprise Architecture 2010) has developed a survey on the current state of enterprise architecture organizations, architects and practices. The purpose is to gather information as a baseline for the evolution of enterprise architecture organizations, architects, and practices, in today's business-driven, service-oriented world.
In my last post I wrote about differences of the search services in the Sharepoint Technologies 2007 - Search in SharePoint Technologies 2007. The architecture of search service is composed for many components (shows on Figure 1), and its important to say that Enterprise Search uses the same underlying Search service as Search in Microsoft Windows SharePoint Services. (great news).
Best of the blogs: Big, small, nascent, niche, and stack players, SOA has them all, David Linthcium points out in this Real World SOA post. Some are good, others are not. "The funny thing is that all of the vendors that read this blog,
I've been invited to give the following talk at BEA Participate: Why is a Service-Oriented Architecture important to an IT infrastructure and what are the elements and products needed to build out an SOA? These questions answered, plus a discussion on how portals are the practical starting point to leveraging SOA. Quite honestly, the title and abstract make it sound like an invitation to engage in a lively game of buzzword bingo, but I assure you this talk will be light on the trite -- you won't hear me use the acronym SOA more than once or twice -- and heavy on the real deal, rubber-meets-the-road stuff about how mere mortals/human beings are actually accomplishing the sort of things that SOA evangelists are preaching these days.
