Summit Tracks
Architecture for Postmodern IT: SOA, WOA, EDA, and Cloud
Three key macro trends—externalization, consumerization, and democratization—are disrupting business-as-usual in IT organizations. The days of monolithic solution architectures are over, at least for those companies that want to remain competitive in the post-crisis economy. This track explores architectural models that leverage postmodern principles and support mobile, social, and cloud computing. Key Issues: -Which application architecture principles best support mobile, social, and cloud computing? -Now that you’ve implemented SOA, what’s next? -How do you leverage SOA application design for cloud?
Sessions
Postmodern Application Architecture
29 November, 2011 (10:15 AM - 11:00 AM)
Externalization, consumerization, and democratization are disrupting business-as-usual in IT organizations. Postmodern IT requires a conscious break with the past and the rejection of old narratives. This Summit track explores the latest trends in application architecture.
Advanced SOA – The Impact of Heterogeneity on SOA Development and Governance
29 November, 2011 (11:15 AM - 12:15 PM)
Early SOA focused on internal, homogeneous development. Mature SOA increasingly integrates heterogeneous services to support composite applications and BPM projects. This heterogeneity requires new approaches to service management and application development.
SOA, WOA and REST: Real-World Scenarios
29 November, 2011 (02:15 PM - 03:15 PM)
SOA is becoming a standard approach to structuring new systems. As more SOA systems are developed, some common patterns of implementation are becoming apparent. These use cases combine the various SOA, Web Architecture and RESTful concepts to create highly flexible systems.
Case study: SOA Integration as the Foundation for Customer Analytics - Wind River Systems, Inc.
30 November, 2011 (08:30 AM - 09:30 AM)
There’s a great deal of excitement today in analytics, broadening a base case for SOA to include significant data analysis and action based on customer activity. In this case study, we’ll talk with key implementers at Wind River, which has been using SOA as a foundation for integrating customer analytics.
Case Study: The Impact of Event Processing on Application Architecture (Bank of America)
30 November, 2011 (02:00 PM - 03:00 PM)
IT systems have used events for decades to support system functions and GUIs, but only now are events becoming first class citizens in high-level application architecture. Gartner’s Roy Schulte sets the stage, followed by Kim Kazmaier from Bank of America who will feature her case study: Implementing the Integration Suite - ESB, Web Services, BPM and EDA at Bank of America.
Applying SOA Design Principles to Cloud Application Architecture
01 December, 2011 (08:30 AM - 09:30 AM)
Hybrid cloud application architecture will not be realized by simply redeploying isolated applications onto IaaS. Cloud computing is not an excuse to leap-frog architecture practices such as service modeling. Applying SOA design principles at multiple levels is the cornerstone of any approach to composing internal and external services.
Roles of Solution and Application Architects
01 December, 2011 (12:30 PM - 01:30 PM)
Enterprise architects want to ensure the consistency of application solutions with architecture strategies and plans, yet do not want to get bogged down in the details of projects. Application architects want to promote consistency and reuse at the project level.
Agile Architecture
01 December, 2011 (01:45 PM - 02:45 PM)
Organizations are seeking to increase development agility, but often fail to address how agile development practices impact architectural decisions. Despite our wishing it were so, software architecture is not static throughout a project. Agile architecture is defined by our willingness and ability to embrace and accommodate architectural shifts. While embracing change is an attitude, the ability to accommodate change requires a software architecture that can adapt to change. Agile architecture is both temporal—when to make architectural decisions—and structural, demanding that the architect and architecture remain flexible and able to accommodate change.
