LogicBlaze fuses SOA, Ajax to LAMP with MySQL partnership |
 |
By Rich Seeley
26 Apr 2006 | SearchWebServices.com |
|
|
LogicBlaze Inc. and MySQL yesterday announced a partnership that brings together many of the hottest commodities in IT: service-oriented architecture, LAMP stack development and Ajax.
|
|
|
|
|
An application based on LAMP or Ajax that provides access to the MySQL database environment doesn't need to be a silo.
Rich Peterson
Vice President of Marketing, LogicBlaze
|
|
|
|
|
|
|
|
|
|
The combination, called LogicBlaze FUSE for MySQL, brings together LogicBlaze's enterprise service bus (ESB) platform, available as an Apache License 2.0 open source download, with the MySQL database. The partnership, unveiled Tuesday on the opening day of the MySQL User Conference 2006 in Santa Clara, Calif., is targeted at architects and developers working with the LAMP (Linux, Apache, MySQL, PHP/Perl/Python) programming model, as well as Ajax, said Rich Peterson, vice president marketing for LogicBlaze.
While MySQL is the database component in LAMP, what LogicBlaze brings to the party is FUSE, based on Apache ServiceMix, an open source ESB. The combination holds the potential to transform LAMP applications into Web services running inside an SOA.
LogicBlaze is touting its lightweight messaging capabilities as a good match for LAMP and Ajax projects connecting to MySQL. For Peterson a key concept is connectivity.
"An application based on LAMP or Ajax that provides access to the MySQL database environment doesn't need to be a silo," he said. "It can be a highly connected application. The FUSE platform is what we incorporate the ServiceMix into. The ServiceMix provides that kind of connectivity through a set of standard binding components and interfaces."
Speaking from the MySQL conference where he was evangelizing the LogicBlaze approach among the architects in attendance, Peterson explained the product mix.
"The configuration itself is FUSE, that's the Apache ServiceMix, (Apache's) ActiveMQ, along with the binding components, service engines, UDDI directory, HTTP server, management console and all the features that are standard," he said. "In addition to that, we're providing the libraries for the integration of the MySQL database."
In the new business model of open source software, LogicBlaze will provide services and support for SOA architects and developers working on LAMP and Ajax projects once they download the software. While the product is FUSE for MySQL, and all the software is scheduled to be downloadable starting in May, it won't be a traditional bundle either.
"The MySQL database is a separate download because it is licensed under the GPL from MySQL, while our stack remains Apache 2.0," Peterson said. "But it's a fairly straightforward download."
For LAMP, Peterson said, FUSE provides native client support for Perl, PHP and Python, as well as Ruby, the popular scripting language which now is included in the LAMP model although it does not fit the acronym.
"So people who have written an application in one of those languages can literally run it, can put FUSE into their application stack and run it with higher reliability and performance because internally now they're running over JMS (Java Messaging Service)," he said.
FUSE also includes continuation technology in its HTTP server to provide the scalability and speed required for Ajax applications, he said. One of the first uses of the combined MySQL and LogicBlaze software is what Peterson calls "the scalable Ajax scenario."
"What continuation does is it basically manages the stress Ajax puts on the HTTP server that wasn't there when all it was doing was serving static HTML," he explained. "Serving static HTML pages going from 100 concurrent users to 10,000 concurrent users isn't that big of a deal because they are only refreshing every so often. But if those connections are Ajax and they're continuously connected and you're streaming XML, now you're trying to manage 10,000 continuous connections to the HTTP server. Continuations gives us a way to get around that. So we see the scalable Ajax scenario as being the first use case for this configuration."
|
|
|
|
