10:55:50 am, Categories: Business, Computers and Internet, Open Source, ETL/EAI/ESB, 561 words Posted by: Joseph A. di Paolantonio
The rest of this first morning of MuleCon2008 seems to be devoted to partner and customer use cases. The afternoon will be breakout sessions separated into a user track and a developer track. This is in stark contrast to last year's MuleCon, where the first day was training on Mule, while the second day was filled with alternating sessions devoted to core developers talking about the roadmap and users telling their stories. This change, coupled with the higher attendance indicates to me the maturation of Mule and MuleSource.
Jahan Moreh, VP Technology of U1 Technologies spoke about high performance messaging using Mule. He started off giving talking about messaging standards such as Java Messaging Service (JMS) and Advanced message Queuing Protocol (AMQP). He gave a very good overview, almost a tutorial, on messaging in general and the trade-offs involved in high performance messaging.
Eugene Ciurana, Director of Systems Infrastructure at Leapfrog Enterprises, Inc. spoke on "Son of SOA: Resource Oriented Computing and Event Driven Architectures" PDF download. Eugene provided an entertaining look at the limitations of SOA and the challenges and rewards of implementing SOA at Leapfrog, from the perspective of Charlie the Farting Dog. Well, not quite, this was an example of the upcoming Tag from Leapfrog reading a book. Leapfrog is very driven to implement new systems in very short timeframes using best of breed components. Of most interest to me is the shift towards consuming resources, blurring the distinction between services and data sources. All components of a system are viewed as resources to be consumed synchronously or asynchronously. there is no distinction between data, objects or services and there is no dependency on a programming language or framework. Programs map logical and physical locations through identifiers in traditional computing models. Resource Oriented Computing defines resources through verbs and logical identifiers, much like REST, but not exactly. Eugene went into a good comparison of how Java, REST and ROC handle Resource, Identify, Resolve, Compute, Immutability. Eugene selected Mule ESB as his ROC Backbone (workflow, transactions, transformations, logging and routing) and for the Resource Container. Extending the web protocols to go beyond the four REST verbs is easy within Mule. The initial ROC implementation took about 60 days, with developers just writing POJOs and everything deployed as a single JAR file. The ESB backbone is actually as many identical implementations of Mule as he needs, thus he can scale the backbone horizontally as much as needed. To summarize Eugene's conclusion, complex systems are easier to code and maintain if implemented as small blocks which can be mapped as resources that can be consumed in a stateless fashion reducing implementation costs by 70% and maintenance costs by 30-40%.
Roy dela Paz of Biogen Idec [Nasdaq: BIIB] provided a "Customer Case Study: Move over Proprietary, Here's Come Mule". The BEA Weblogic Integration Platform v8.1 has been in use at BIIB for internal and external data integration since 2004, but the learning curve has been steep [very abstracted, proprietary, non-standard development environment], it's been unstable [Nagios scripts have helped here], and it hasn't scaled well. Mule came back into play through a "water cooler conversation" and investigation showed that Mule provided the required capabilities in a lightweight, stable, scalable package using standard XML and POJO development skills. Roy compared the complexity of Weblogic vs Mule as that of the Sideways Bicycle vs a normal single-speed bike.
http://press.teleinteractive.net/.Mk3ucWch7fhVbndsciwcFvbhxzcQxbcj0rf7uyb2e_cnb3/trackback.php/821
No Comments/Trackbacks/Pingbacks for this post yet...
The Open Source Solutions Blog is a companion to the Open Source Solutions for Business Intelligence Research Project, sponosred by InterActive Systems & Consulting, Inc. This Blog, a Wiki and Lens will be used to develop, support and publish the findings of our research into enterprise open source projects.
InterActive Systems & Consulting, Inc. (IASC) performs research in the areas of data analytics, collaboration and remote access.InterASC Professional Services, a service mark of IASC, provides strategic consulting and project management for data warehousing, business intelligence and collaboration projects using proprietary and open source solutions. We formulate vendor-independent strategies and implement solutions for information management in an increasingly complex and distributed business environment, allowing secure data analysis and collaboration that provides enterprise information in the most valuable form to the right person, whenever and wherever needed.
TeleInterActive Networks, a service mark of IASC, hosts open source applications for small and medium enterprises including CMS, blogs, wikis, database applications, portals and mobile access. We provide the tools for SME to put their customer at the center of their business, and leverage information management in a way previously reserved for larger organizations.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 |
