There are almost as many open-source and commercial frameworks, JSRs, standards, and compliance tools as there are problem domains. There is no such thing as "the right architecture," regardless of what pundits, trolls and consultants want you to believe. In the best case your analysis and biases will lead only you to "the most appropriate" architecture for a given problem domain and for a period of time. Architectures must evolve to fit emerging engineering and business needs. This presentation features case studies that show how given architectures were chosen, their implementation, and the results of those decisions over time for various problem domains. Come to explore open-source, commercial and hybrid successful architectures that worked - and, almost as important - one or two that didn't make it.

Problem domains:

• Banking transaction backbone: JMS vs. COBOL-based messaging
• Mass streaming media distribution over the Internet
• High performance product/service fulfillment systems
• Sending millions of marketing emails per hour
• Integrating mobile services with the rest of your enterprise