Service and solution development are closely related, but do not necessarily occur at the same time. Some services may be conceptualized and even implemented in anticipation of their need, while others are developed concurrently with the solutions that require them. This talk, based on joint work between TIBCO and CBDI, discusses the interactions between solution and service development processes, with particular emphasis on the artifacts that are exchanged and the timing of these interactions.
Forrester's surveys show strong adoption of SOA, particularly by large organizations. Client experience is yielding good (and bad) practices for applying SOA principles for a variety of organizations. Most clients are reaching much further than simple application integration with their SOA strategies. Their goal: Create architectures that give business management unprecedented flexibility in the IT systems that either support or are the business. This session describes the state of SOA in the enterprise market, and discusses the possibilities and prerequisites of architectures based on SOA for both "Type A" and more conservative organizations.
This presentation introduces a new composition approach to building SOA services, explains composition, and provides a methodology to evaluate today's tools for developer productivity and ease of deployment/management. Frank Cohen, CEO at PushToTest and the leading authority on testing SOA applications, shows the results of recently completed PushToTest study of the competing SOA development and deployment platforms.
Delta is in the process of implementing the next version of their backbone, Delta Nervous System 2.0, that supports everything from booking, checking in and upgrades to flight rescheduling and baggage handling. Learn more about Delta’s approach to mission critical SOA, some of their best practices, and their use of TIBCO ActiveMatrix™.
Recent studies show that up to 40 percent of the code written for the average service developed using an application server is unnecessary or redundant and makes SOA less flexible to change. Just as a civil engineer wouldn’t design an office tower with independent plumbing, electricity and insulation for each individual office, software engineers should avoid writing services without a common framework for communications, deployment and management. This session will explore the concept of service virtualizatio, and how it can be used to manage the complexity of a heterogeneous, distributed SOA that includes Java, .NET, and various legacy and packaged applications deployed across the enterprise. Attendees will learn the different architectural components of service virtualization – mediation, deployment, governance and service management – the importance of service containers, and the standards that make service virtualization possible.