Welcome!

Thomas Erl

Subscribe to Thomas Erl: eMailAlertsEmail Alerts
Get Thomas Erl via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Thomas Erl

For a complete list of the co-authors and contributors, see the end of the article. Microsoft's Software-plus-Services strategy represents a view of the world where the growing feature-set of devices and the increasing ubiquity of the Web are combined to deliver more compelling solutions. Software-plus-Services represents an evolutionary step that is based on existing best practices in IT and extends the application potential of core service-orientation design principles. Microsoft's efforts to embrace the Software-plus-Services vision are framed by three core goals: User experiences should span beyond a single device Solution architectures should be able to intelligently leverage and integrate on-premise IT assets with cloud assets Tightly coupled systems should give way to federations of cooperating systems and loosely coupled compositions The Windows Azure platfor... (more)

Cloud Computing, SOA and Windows Azure - Part 3

For a complete list of the co-authors and contributors, see the end of the article. A cloud service in Windows Azure will typically have multiple concurrent instances. Each instance may be running all or a part of the service's codebase. As a developer, you control the number and type of roles that you want running your service. Web Roles and Worker Roles Windows Azure roles are comparable to standard Visual Studio projects, where each instance represents a separate project. These roles represent different types of applications that are natively supported by Windows Azure. There ... (more)

SOA Pattern of the Week (#1): Service Façade

One of the fundamental goals when designing service-oriented solutions is to attain a reduced degree of coupling between services, thereby increasing the freedom and flexibility with which services can be individually evolved. Achieving the right level of coupling "looseness" is most often considered a design issue that revolves around the service contract and the consumer programs that form dependencies upon it. However, for the service architect there are opportunities to establish intermediate layers of abstraction within the service implementation that further foster reduced... (more)

SOA Pattern of the Week (#5): Service Decomposition

A service inventory is a living body of services that individually will need the freedom to evolve independently over time. What we learned when documenting the SOA design pattern catalog is that there are patterns that emerged not only at design-time but also during this post-implementation evolutionary stage in a service's lifecycle. There is one common scenario that repeatedly surfaced in many projects: When we model and design services during early stages of SOA adoption we are constrained by current infrastructure and technology. These constraints require that we limit the s... (more)

Exclusive SOA Web Services Journal Briefing – Thomas Erl On SOA

With the unwavering prominence of service-oriented architecture (SOA) there is an increasing interest in understanding what exactly it means for something to be considered "service-oriented." Thomas Erl recently completed a lengthy research project for SOA Systems Inc. into the origins of SOA and the current state of service-orientation among all primary SOA technology platforms. This body of work contributed to the mainstream SOA methodology developed by SOA Systems and was also documented in Thomas's new book, Service-Oriented Architecture: Concepts, Technology, and Design. We ... (more)