ZapThink’s Service-Oriented Architecture Roadmap
ZAPTHINK’S ROADMAP TO SOA ADOPTION Companies today are struggling with the best way to implement IT infrastructures that enable business agility. Service-oriented architectures based on Web Services provide cost-effective approaches to achieving companies’ agility goals. ZapThink’s Roadmap to SOA adoption is a one-of-a-kind, full-color 24×18″ poster that provides organizations of all sizes and types an at-a-glance view at how to approach implementing Service-oriented architectures in a way that provides return-on-investment (ROI) at each step along the path toward agile IT infrastructures. Included on this easy-to-read poster are the steps and phases by which companies can move from today’s brittle infrastructures to loosely-coupled, coarse-grained, asynchronous SOAs. The poster covers concepts in point-to-point Web Services implementations for integration, securing, managing, and adding process layers to these services, implementing registries and management for loose coupling, moving to asynchronous invocations for greater reliability, and concepts in virtualization, contract-first development, SOA governance,…

Read More

ZapThink SOA Roadmap
The ZapThink Roadmap for SOA Implementation presentation covers the following topics: The Practice of Architecture The Fundamental Tenets of SOA SOA Prerequisites Contracts and Policies Securing and Managing Services Metadata Management, Registries, and Repositories Service-Oriented Process This is a 46-slide presentation in pdf format.[hide -2]Download File[/hide][hide +1]Purchase: $195[/hide]…

Read More

The Sunset of Legacy
Among the most persistent of humanity’s aspirations is the quest for immortality. We are all too conscious of the limitations of our bodies and our lives and seek some religious faith, fountain of youth or cryogenic miracle that can sustain us forever. And yet, immortality is an unattainable goal. As such, we shift our ambitions for endless life to the things we do control: our IT systems and solutions that we implement in hopes they stay alive forever. We have long been trained to build our IT systems to last. However, this approach to IT ironically means that we are building things that by definition will become obsolete, given the constant, unpredictable changes in business and IT. Service Orientation, however, promises to change this build-to-last approach to IT. By building inherently flexible systems, maybe we finally have a way to unlock the shackles of legacy. The fact still remains, however,…

Read More

A Roadmap to SOA Success
This 78-slide presentation covers: The business impact of SOA and why you should care SOA Roadmap: The lowest risk path to SOA Solutions for tactical issues faced when implementing SOA Presentation given in Calgary, AL on September 29, 2005. RoadmapSOASuccess-OBS-02005-ZTP-0193-1…

Read More

What Belongs in a Service Contract?
Service-Oriented Architecture (SOA) has finally turned a corner: companies are shifting from the tentative first steps of Service enabling a few systems here and there to strategic SOA rollouts of all sizes that now have the blessing of senior management in the IT departments, and sometimes business executives themselves. In the hundreds of conversations that ZapThink has had in the past year, we have recognized a clear, decisive pattern of organizations moving toward SOA and away from the tightly-coupled, brittle integration approaches of yesterday. We’re no longer getting questions about the “whats” or “whys” of SOA, but rather the “hows” and “whens.” In fact, companies no longer discuss whether or not to embark on an SOA initiative. The eventual move to SOA is fast becoming a fait accompli. In the midst of this decisive move toward SOA, we are now starting to get more difficult, tactical questions about how to…

Read More

How Do You Build a Service?
This is a 33 slide presentation on the things to consider when building a Service, and understanding what’s the Business side of the Service? Granularity Context/domain dependency Ownership How to identify services (process) How to differentiate services Business Processes and SOA Top-down vs. Bottom-up Service development Composition, Orchestration, Choreography, and Process Decomposing Processes for Service definition Managing Processes Who is in charge of the process? E2Open case study HowBuildService-082005-ZTP-0184-1…

Read More

How Many Architectures Do You Need?
Not long after we debunked the distinction between Event-Driven Architecture (EDA) and Service-Oriented Architecture (SOA) did we become aware of yet another architectural TLA (three-letter acronym): Process-Oriented Architecture (POA). Proponents of POA describe an architecture that leverages processes as the fundamental element of the architecture. POA leverages SOA, to be sure, but relegates SOA to a technical role that deals exclusively with exposing IT functionality as Services. If your jargon alarm is ringing in your head at this point, well, you’re not alone. SOA, POA, EDA, not to mention n-tier architectures — just how many architectures do we need, anyway? It seems that as information technology (IT) finally gets a handle on what software architecture is, now everybody wants to create a new one. The danger of this trend is clear: if different camps within IT fragment along architectural lines, then we run the risk of adding siloed…

Read More

So, Where are the Architects?
If you’ve been paying attention, one of the things that the movement to the sort of agile IT that Service-oriented architecture (SOA) enables is a new set of roles and responsibilities in the organization. We often blame today’s IT departments and their technology purchases for being responsible for the integration rats’ nests that are the cause of today’s inflexibility, and we frequently chastise the business folks for making expedient, short-sighted decisions that only make the problem worse. So, is there a way out of this puzzle? Is there anyone in the organization that can hope to get the vision of Service Orientation right, or is this all a hopeless struggle? Fortunately, there is hope, and it comes in the form of enterprise architecture. As we’ve frequently discussed, the most critical part of making SOA work is doing architecture well. So, if there’s a need for architecture, then it figures…

Read More

Business Process: Sweetness & Light or Evil Hellspawn?
Sometimes it seems that everyone in IT is a cynic. ZapThink frequently discusses how through the power of abstraction, loosely coupled interactions, and composition, IT can finally respond to changing business needs in the time that the business requires those changes. The cynics are only too happy to point out that we’ve heard those promises before, and then they ask what’s so different this time? Our response to the cynics centers on the role of business process within the organization. Business processes have always been an important, if understated, asset of enterprises. The nature and methods that a company runs its business with changes on a daily basis at various different levels in the company — from high-level strategic changes to lower-level implementation details. As a result of these changes, enterprises constantly struggle to make their companies more responsive to business changes by connecting their business requirements to the…

Read More