Overview of SOA
Module #1 from the Licensed ZapThink Partner Program’s licensed training materials. This module covers: Business Constant: Change The Integration Challenge Integration Approaches of Yesterday SOA: Definition SOA Features SOA: Implication SOA: Benefit Characteristics of SOA SOA: A Technology View The Difference is Web Services Web Services = SOA? Service orientation — the next big thing? The Business Benefits Business Agility SOA Hotspots The ZapThink SOA Roadmap CurrentStateSOAPractice-Europe-022006-ZTP-0212-1…

Read More

Understanding Basic SOA Concepts
Module #2 from the ZapThink Licensed Partner Program training materials. This module covers: SOA shifts the way we think What are Services? Characteristics of Services Service Orientation How to Think Service-Oriented SOA Abstraction Layer Service Orientation Idées Fortes What about Coupling? Service Contracts & Loose Coupling Benefits & Challenges The Challenges with doing SOA right Emerging Best Practices Service Invocation Styles Interoperability vs. Portability Event-Driven Architecture vs. SOA CurrentStateSOAPractice-Europe-022006-ZTP-0212-1…

Read More

The Human in the Machine
In the late 1700s, a clever inventor built a mechanical device he called The Mechanical Turk that could play a mean game of chess. It was so good, in fact, that people such as Benjamin Franklin and Napoleon Bonaparte traveled to play the machine, only to lose to it. The Turk was certainly a curiosity of the day, since there were no computers, no microprocessors, hard drives, or networks to speak of. So, how did this curious device work? It turned out that it was all an elaborate hoax, with a chess master hiding inside the machine operating an intricate set of springs and magnets to move the mannequin attached to the device. Playing chess at the grandmaster level, of course, is extraordinarily difficult, and it was only in the last decade that computers surpassed the best human players in ability. Ironically, computers are still unable to perform other,…

Read More

Right-Sizing Services
We all know the tale of Goldilocks and the Three Bears: the story of an interloper that seemed to want her chair, porridge, and bed just so, despite her invasion of ursine privacy. Just as one-size-fits-all food or accommodations could not sate Goldilocks, so too are early proponents of Service-Oriented Architecture (SOA) realizing that they must size their Services just so in order to meet their pressing business problems so that they can maximize reuse and minimize unnecessary expense. Not only that, these early adopters are realizing that they must tackle significant aspects of Service infrastructure and architectural best practices from the very beginning, even if they are deploying a small set of Services. After all, a successful SOA implementation requires not only the right Services, but implementing them in the right way. One of ZapThink’s repeated refrains is that SOA is an aspect of enterprise architecture, which itself…

Read More

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

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

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

Creating Contract and Policy Metadata
One of the first questions that archtiects and developers are posed with when building an SOA is exactly how to build a “Service”. Companies building loosely-coupled Services know that contracts and policies, built in metadata, are key to making SOA work. So, what exactly goes into Service contracts and policies, and what specifications are currently available to meet Service contract needs? This 24 slide presentation outlines some of the key issues in creating and implementing Service contracts as well as the steps companies should take to create them. HowBuildService-082005-ZTP-0184-1…

Read More

Reactivity: Efficiently Mediating Identity in a Heterogeneous, Service-Oriented Environment
As companies move to architectures that enable loosely coupled, composite, Service-oriented interactions between distributed systems, they quickly realize that identity management is essential to making such interactions reliable, predictable, and secure. The only way to build applications that rely on functionality from disparate systems in the enterprise is to separate identity and policy from the underlying systems that have heretofore locked those two capabilities within their own, proprietary environments. However, implementing the sort of federated enterprise identity management capabilities that Service-Oriented Architecture requires is difficult because existing identity and policy information reside in a wide range of systems. Reactivity is one vendor that provides new technologies and approaches for accessing and mediating identity and policy information that companies require. [hide -1]Download File[/hide][hide +0]Register to Access this Document[/hide]…

Read More