Day two is in the bag, the B52’s are B-50-done. Perficient and MTS Allstream gave a session about SOA Patterns that I thought was today but was actually yesterday. Oops. Here’s the abstract if you have a time machine:

TSP-2518 - Effectively selecting integration patterns
Brent Legris, Perficient, Inc., Senior Technical Architect, Olivera Zatezalo, MTS Allstream Inc., Sr Manager, Integration, BT&IT

The foundation of knowledge that rests beneath service oriented architecture (SOA) encompasses a myriad of integration patterns not only messaging, enterprise service bus and orchestration, but shared databases, ETL, operational data stores, and others. Effectively selecting between integration patterns is a critical capability to develop as your SOA evolves, in order to avoid running around with a hammer thinking everything is a nail. This session interactively develops various integration scenarios, discussing pattern alternatives and their effective implementation. We will discuss the tradeoffs of different approaches, but close with guidelines that can be consistently followed to exploit the capabilities of an enterprise infrastructure.

Level: Intermediate

What I like about this presentation is that it’s about patterns and decisions and trade-offs, but primarily focuses on WebSphere Integration Developer and WebSphere Process Server. I like it when patterns come ‘out from the mist’ and you actually see them implemented in a system. I’m a developer at heart. Hopefully the presentation slides will be made available on the Impact site.

The other thing I heard a lot about was WebSphere sMash the IBM commercialized, supported version of Project Zero.

As for other impressions of Day 2, I don’t really have any. It seemed like a normal day at a conference in Vegas to me.

Related Posts

• Impact 2008: My impressions of Day One - SOA Jam
• Impact 2008: Impressions of Day 2 - SOA Jam
• Impact 2008: My impressions of Day One - Blogs & Twitter
• Impact 2008: SOA Jam Day 3
• Impact 2008: Final Day - Blogs

Project Zero is:

..about agile development of the next generation of dynamic Web applications. Project Zero introduces a simple environment for creating, assembling and running applications based on popular Web technologies. The Project Zero environment includes a scripting runtime for Groovy and PHP with application programming interfaces optimized for producing REST-style services, integration mash-ups and rich Web interfaces.

Why the brew-ha-ha about yet another runtime? My interpretation of the goal of Project Zero is to take the enterprise concepts contained in a “heavy-weight’ solution like WebSphere and let those concepts be run on a light-weight server using scripting languages and an XPath-like syntax. The goal is to bring the cost of integration solutions for small to medium sized business down by stripping out and simplifying the interface to the runtime.

Project Zero simplifies next-generation Web application development and increases developer productivity by providing:

* A simplified approach to development through the introduction of agile programming and assembly techniques which are attractive to Web developers.
* A platform optimized around popular technologies found on the Web that are recognized for their ability to lower complexity and shorten development time. This platform uses REST and ATOM to form the basis of the service invocation model; JSON and XML as the data interchange format; and Ajax as the model for a rich client.
* Building blocks that enable developers to get applications up and running quickly by leveraging reusable components such as code snippets, widgets, libraries, templates and pre-built services.

One of my goals this year is to get more familiar with Project Zero. I only know about it from marketing slides and ‘firehose’ presentations at conferences. It sounds like a very intriguing product.

You can learn more about it from their FAQ

Related Posts

• Impact 2008: Impressions of Day 2