Once upon a time, data modeling played a central role in the process of developing applications. Thus far in the SOA era, there has been a heavy emphasis on process, and data has all-too-often been lost in the SOA shuffle. In this talk, we present a data model for SOA - i.e., a service-oriented data model. This model formalizes the notion of a data service, modeling data in SOA as a layer of interrelated data services. We explain the key components of this model, including a taxonomy of data service operation types, a mechanism for capturing the entities that the data services are 'about', and an approach to modeling relationships in SOA. The content of this talk is based on the data services model embodied in the BEA AquaLogic Data Services Platform (ALDSP), and the approach is based on lessons learned over a period of several years of working with data services and customer use cases.

The workshop is a hands-on session focusing on data access and data services issues, problems and solutions. It's an opportunity for audience members to view and discuss problems with a panel of experts. The goal of the session is to engage the audience using walk throughs, examples, and a question and answer (Q&A) session. The operative principles are interactivity and dialogue.

The new wave of Web applications are built on technologies such as AJAX and Microsoft Silverlight, which enable developers to build better, richer user experiences. These technologies bring a shift in how applications are organized, including a stronger separation of presentation from data. Technologies such as Language Integrated Query (LINQ) and ADO.NET Entity Framework and Data Services simplify the job of developers. The ADO.NET Entity Framework raises the level of abstraction for data programming. It is the evolution of ADO.NET that allows developers to program in terms of the standard ADO.NET abstraction or in terms of persistent objects (ORM) and is built upon the standard ADO.NET Provider model. The Entity Framework introduces a set of services around the Entity Data Model (EDM) (a medium for defining domain models for an application).

'As SOA rapidly becomes the standard for enterprise architectures, the need for robust technologies for data access and data integration has become more critical then ever before,' says John Goodson, executive leader of DataDirect Technologies. Goodson will be keynoting the inaugural DataServices World one-day event being held in June 24 in New York City, co-located with the 13th International SOA World Conferemce & Expo at The Roosevelt Hotel in midtown Manhattan.

A panel of experts and executives from organizations that are leading providers and consumers of technology will discuss trends and important technologies for enterprise and Internet computing. The experts will discuss the role of databases and database technology trends that enhance SOA and web development. The panel session will also focus on preferred solutions for architecture and middleware to enable applications and services to access data from SQL and other data sources.

The ever-increasing movement towards implementing complex SOA-based applications has triggered a direct attention of leading industry researchers and practitioners to the subject of layering in such applications, in general, and the relationship between the fields of database engineering and SOA, in particular. Common notion of interoperability, loose-coupling between consumers and providers, and complexity-hiding, and demands for enabling extensive reuse of application services to address unforeseen business requirements for new user types, for new types of information and for new composite views has brought to the forefront the concept of Data Services Layer (DSL) as a distinct architectural layer. DSL is an essential part of an application architecture that combines data access functions and corresponding database structures and promises ensuring the next harvest for SOA ROI.

URIs are the lingua franca of the web. They are in every web page and every HTTP request. In a practical sense, they represent the realization of the web. Without them, the web would cease to exist. The situation is very different in the world of the RDBMS. Here, URIs are interlopers. Some RDBMS have provided basic support for URIs via their object extension facilities; however, URIs are still not considered a formal part of RDBMS schema design. This talk explores how URI could evolve to become as important to RDBMS Schemas as it is to the web. One aspect of URI 'types' this presentation will cover is the use of Web Application Description Language (WADL). WADL has been described as SQL Schema meets REST. WADL is metadata describes the functional and structural aspects of a URI 'type' that a web site or other provider offers through HTTP.

One aspect of the debate over software productivity and assembly is whether or not visual tools can help. I think that they do - visual abstractions can be very meaningful - but I do not know of any visual system that actually solves the complete problem (i.e none have solved the customization/round trip problem). UML tools are furthermore too object oriented for some applications - such as services and REST.

Late Thursday Yahoo released the text of the letter it sent to Carl Icahn telling him he's misguided and that the current Yahoo board knows better what good for the company. It repeats what Yahoo has said before - that it is willing to sell for the right price, which lately has been $37 a share. Meanwhile, Yahoo and Google are reportedly still talking.

Even though 'Service' comes first in SCA (Service Component Architecture), SCA is a distributed component model. It's about designing components (and composites) rather than designing services. It doesn't feel like it was designed to build a SOA. It feels like its main goal was to define a distributed component model. And as we all know, the distributed component models failed in the past. I think SCA will too.

While SOA has traditionally had something of a data obsession. While the focus has been on service-enablement of structured and transactional data and processes, documents and document-centric processes have been conspicuously absent from the SOA agenda. With structured data in order, organizations are now beginning to take a closer look at the role of unstructured assets as part of SOA.

Interoperability is the ability of two or more systems to work with each other. In the loosely coupled environment of a service-oriented architecture (SOA), separate resources don't have to know how each of them work, but they do need to interoperate with each other by having enough common ground to exchange messages without error or misunderstanding.

Adopting SOA is a lot like gardening. It takes time, skill, a lot of hard work, and the process can be messy and even a bit frustrating at times. I know you've probably heard tons of different analogies that attempt to put SOA and governance into everyday terms and I'm sure that growing the SOA 'garden' through governance won?t be the last.

A round-up of the Service Oriented Architecture related themes & topics being discussed in NYC June 23-24, 2008 by the world-class speaker faculty at the 13th International Conference & Expo being held by SYS-CON Events in The Roosevelt Hotel, in midtown Manhattan.

From Application Virtualization to Xen, a round-up of the virtualization themes & topics being discussed in NYC June 23-24, 2008 by the world-class speaker faculty at the 3rd International Virtualization Conference & Expo being held by SYS-CON Events in The Roosevelt Hotel, in midtown Manhattan.

SOA is mostly associated with technologies such as BPEL, SCA and Web Services. But does SOA really imply these technologies? In this session we will show how you can use the service oriented approach while staying inside the Java world. jBPM is a powerful lightweight framework that can be used to orchestrate services in the broadest sense. It is highly extendable, very versatile and can be easily embedded in client and/or server applications. Attendees will learn how jBPM can be used in a pure workflow scenario as well as in a situation involving automated business steps.

The continuing success of SOA World Conference & Expo, now in its 13th successive iteration - this time in June, on the East Coast, in the historic Roosevelt Hotel in New York City - has led SYS-CON Events to expand its reach by adding a co-located parallel event, DataServices World. The full details of this major new initiative are as follows...

An increasing number of verticals are using Data Services - services that deal with the production or consumption of data - to solve real business problems and deliver key information...all completely transparent to the user. Data is after all the primary component of architecture, including SOA, as StrikeIron CEO David Linthicum recently underlined in an exclusive Q&A with SYS-CON.com.

As SOA rapidly becomes the standard for enterprise architectures, the need for robust technologies for data access and data integration has become more critical then ever before. Due to the vital role that data plays both in business and systems operations, database architectures, information specialists, data integration experts, and anyone responsible for data persistence in an organization are increasingly being called upon to contribute to their organization's SOA initiatives - whether or not this was intended at the onset. In this presentation, we will review the technologies, best practices, and patterns that are shaping the way we utilize enterprise data.

Both Reuters and the Wall Street Journal are reporting that Carl Icahn - the greatest stockholder activist of our generation - is going to pull the pin to try to force Yahoo into negotiating a deal with Microsoft. It's unclear whether Yahoo's two biggest shareholders Capital Research & Management and Legg Maison Capital Management will support Icahn.

Once upon a time data modeling played a central role in the process of developing applications. Thus far in the SOA era, there has been a heavy emphasis on process, and data has all-too-often been lost in the SOA shuffle. In this talk, we present a data model for SOA - i.e., a service-oriented data model. This model formalizes the notion of a data service, modeling data in SOA as a layer of interrelated data services. We explain the key components of this model, including a taxonomy of data service operation types, a mechanism for capturing the entities that the data services are 'about', and an approach to modeling relationships in SOA. The content of this talk is based on the data services model embodied in the BEA AquaLogic Data Services Platform (ALDSP), and the approach is based on lessons learned over a period of several years of working with data services and customer use cases.

The ever-increasing movement towards implementing complex SOA-based applications has triggered a direct attention of leading industry researchers and practitioners to the subject of layering in such applications, in general, and the relationship between the fields of database engineering and SOA, in particular. Common notion of interoperability, loose-coupling between consumers and providers, and complexity-hiding, and demands for enabling extensive reuse of application services to address unforeseen business requirements for new user types, for new types of information and for new composite views has brought to the forefront the concept of Data Services Layer (DSL) as a distinct architectural layer. DSL is an essential part of an application architecture that combines data access functions and corresponding database structures and promises ensuring the next harvest for SOA ROI.

AMD has kissed Mario Rivas good-bye and turned processor development over to Randy Allan, the head of its star-crossed server and workstation business, reporting to president and COO Dirk Meyer. Allan is now the new head of AMD's Computing Solutions Group, responsible for the bulk of the company's revenues.

'Data services apply the same philosophy of reuse and flexibility that SOA offers, but to the data tier,' explains John Goodson, executive leader of DataDirect Technologies, in this Exclusive Q&A in the run-up to the inuaugural DataServices World on June 24th in New York City, of which Data Direct is the Diamond Sponsor. 'Data services,' Goodson continues, 'provide a level of abstraction that frees developers from concerning themselves with the physical location or format of the underlying data.'

While SOA can deliver dramatic cost reduction of an organization's business operations, it is a complex, multidisciplinary undertaking, and therefore introduces significant risk. This session presents a list of the most important risk factors and ways to mitigate them BEFORE it is too late. The session will be of interest to anyone planning an SOA initiative, primarily CIOs, Technical Managers, Project Directors and Technical Architects.

Popular assumptions can often be dangerous. We will start by considering how the many unique architectural characteristics of SOA, such as loose-coupling, can actually be a two-edged sword affecting the requirements, nature and success of many important aspects of the architecture, especially runtime governance. In fact, the success of any SOA requires that one must gain an understanding of the true nature, performance characteristics and availability of the business transactions that flows in real-time through these highly distributed services and their supporting IT infrastructure. Similarly, security and governance usually play a critical role in the proper operation of a SOA. Although one may support these critical SOA functions using many different technologies and standards, there is no doubt that for most users today the popular WS-* standards will play a central role. We will conclude by considering how all of these standards might best work together to solve these real-world problems in your SOA. In the process, we will speculate upon some the strengths and weaknesses in the current Web services stack, the nature of the standards process and what trends might be most relevant to your own future success.

Exploring the boundaries between the Enterprise and the Internet, this talk focuses on Architectural approaches from the service pattern, process pattern and event pattern to help SOA practitioners understand topics such as Web 2.0, AJAX, SaaS, Social Networks and how they connect with the Enterprise. The emerging patterns of architecture can enable the savvy architect to empower their IT to embrace an accelerating vision of the network economy.

While EDI transactions account for most worldwide commercial activity, XML-based alternatives are beginning to gain traction. According to Forrester Research, stateful XML, stateless XML, and even flat file exchanges are all projected to grow at a faster rate than EDI over the next few years. The firm predicts stateful XML transactions will be required for a growing number of B2B process-oriented transactions and are projected to exceed the growth of EDI transactions over the next five years.

The success of SOA runs two ways. SOA serves as the catalyst for organizational change, yet an organization must be ready to embrace these new dimensions opened up by SOA. The latest survey data shows most organizations are just starting on their SOA journeys. Why do enterprises set out to build a Service Oriented Architecture, but end up with a 'Service Averse Architecture'? There are many promises being made about the potential of SOA these days, followed by disillusionment as these promises don't pan out. However, SOA is more than a single IT project or even a series of implementations. Rather, SOA represents a long-term change in thinking and management of all aspects of the enterprise. SOA not only decomposes technology into loosely coupled systems, but also decomposes organizations into 'loosely coupled businesses.' This session will look at the latest survey data on ways organizations are embracing service oriented architecture, and how far along the road most are from full-functioning SOA.

Dramatic industry changes - including vendor consolidation, outsourcing and the growth of open source - highlight the need for a better way. When a SOA implementation costs too much, the culprit is often the old-fashioned, proprietary and expensive server or hub-based middleware. A better, distributed approach to SOA infrastructure can help reduce cost and increase the benefit of SOA implementation. This presentation includes an overview of the industry trends driving us toward SOA and explains why traditional middleware systems do not meet modern requirements as well as a distributed approach to SOA infrastructure.

Service Oriented Architectures (SOA) can deliver tremendous value in flexibility, adaptability and cost savings. But SOA environments are complex by definition, with lots of loosely coupled components and a potentially vast combination of platforms, software, databases, applications and networks. One of the biggest challenges inherent in realizing the benefits of SOA is effectively managing all of these diverse components to ensure the high availability and performance of the applications running in them to meet crucial Service Level Agreements (SLAs). This session will explore Complex Event Processing (CEP) engines and offer practical insights into how CEP can be leveraged to enable rapid real-time problem correction and predictive problem prevention that is vital to successful SOA implementations.

The new wave of Web applications are built on technologies such as AJAX and Microsoft Silverlight, which enable developers to build better, richer user experiences. These technologies bring a shift in how applications are organized, including a stronger separation of presentation from data. Technologies such as Language Integrated Query (LINQ) and ADO.NET Entity Framework and Data Services simplify the job of developers. The ADO.NET Entity Framework raises the level of abstraction for data programming. It is the evolution of ADO.NET that allows developers to program in terms of the standard ADO.NET abstraction or in terms of persistent objects (ORM) and is built upon the standard ADO.NET Provider model. The Entity Framework introduces a set of services around the Entity Data Model (EDM) (a medium for defining domain models for an application).

URIs are the lingua franca of the Web. They are in every Web page and every HTTP request. In a practical sense, they represent the realization of the Web. Without them, the Web would cease to exist. The situation is very different in the world of the RDBMS. Here, URIs are interlopers. Some RDBMS have provided basic support for URIs via their object extension facilities; however, URIs are still not considered a formal part of RDBMS schema design. This talk explores how URI could evolve to become as important to RDBMS Schemas as it is to the Web.

As Service-Oriented Architectures gain ground, it becomes obvious that their performance is the key to their success. I'm going to briefly write about two sessions that I attended in JavaOne 2008. They outline two totally different approaches from two very different companies. You're going to see that a well performing SOA implementation requires considerable work and performance tuning expertise.

HP CEO Mark Hurd has finally done something that Wall Street doesn't like - he's buying EDS, the IT infrastructure outsourcing outfit founded in 1962 by one-time presidential hopeful and outsourcing pioneer Ross Perot, for around $13.9 billion cash - a venture that some people think is poor use of money better spent elsewhere.

I've worked for Fortune 500 companies engaged simultaneously in 50+ of IT projects as well as small companies with one or two products and I don't believe there is a need for any organization to have a full-time software architect. Once the modeling is done, it is the work of coding and testing that truly takes the full-time effort. Once underway, 100 hours a month of time is enough for any architect to respond to most needs of all ongoing projects.

Back in the 90s I was on a big project to standardize enterprise software. We wrote a few papers about it, and a chapter in a book. We often used the 'Henry Ford' analogy, which relates to the impact standards for interchangeable parts had on hard goods manufacturing. The Henry Ford analogy says that the hard job in mass assembly is getting the interchangeable parts standardized - thereafter creating the moving assembly line is the easy job.

In this wide-ranging interview with SYS-CON.com David Linthicum, CEO of StrikeIron, addresses the hot new Data Services trend and the all-important notion of enterprise mashups, which he pinpoints as the defining technology of the year ahead. 'I'm surprised people are paying me for this work, I'm having a blast,' quips Linthicum.

Service orientation is one of the most popular trends of these recent years, but there are not any metrics on it. Hence you can not consume SOA in a project with a specific measuring. On the other side, Unified Process (especially RUP) has powerful abilities on such developments. In our discussion Chris Shayan is going to demonstrate that we can combine SOA and RUP with each other and finally make a Service Oriented Unified Process.

It seems that Service Oriented Architecture (SOA) continues to be this year's hot buzzword, rather than a well-defined, meaningful and valuable part of the Enterprise Architecture landscape. Before the term fades away completely, perhaps we should agree what's valuable about the move to SOA and how to make the leap, and make the leap valuable. OMG's SOA Consortium is making great strides in defining SOA to be a valuable business strategy for business agility, taking advantage of Enterprise Architecture, Business Process Management and other concepts; and the OMG itself is making headway on modeling standards for services (as opposed to yet another set of standards for moving bits around wires).