When Microsoft first rolled out its Windows Azure cloud computing architecture, it stepped a bit out of persona, going so far as to support work on a Java SDK for non-C# developers looking to place apps on Microsoft’s new cloud. Still, most updates aimed at easier Azure cloud application deployment are of the .NET variety – not Java or J EE.
Exceptions to the ”.NET-mainly” trend for Azure have emerged. Earlier this year, interoperability specialist JNBridge released JNBridge Pro 6.0 with support for cross platform cloud implementations that span the .NET and Java languages. This week, Java in-memory data grid pioneer GigaSpaces announced tools that take complex Java application and integration software as-is and places it on the Windows Azure cloud platform.
Known as Cloudify for Azure, the software prepares applications by providing a Groovy-based domain-specific language for bundling deployment scripts, as well as basic out-of-the-box patterns for launching Java-on-the-cloud elements that can include the Apache server, Cassandra distributed database, the Spring framework, the XAP in memory data grid and others.
The developer can work in a familiar Java environment, which distinguishes Cloudify for Azure from first-generation clouds that required the development team to adopt the cloud provider’s language of choice. That can be a difficult aspect of what has come to be known as Platform-as-a-Service (PaaS).
”People get the direction to move to the cloud. Then they find out it can be much harder than they thought,” said Paul Burns, Analyst, Neovise. ”If they could move their applications ‘as-is,’ it is not that hard after all.” Continued »
Closing the gap between the needs of the business user and the capabilities of the developer is a driving demand these days. It is also a major theme of Forrester Research’s upcoming Application Development & Delivery Forum 2011 (Sept. 22-23 in Boston, MA). Continued »
While working for a large consultancy and later on his own during the 2000’s dot.com bust, Steve Yaskin commonly had to find a way to access undocumented and orphaned CRM and ERP applications in order to integrate them with Web and other applications. The approach he took to tooling, enhanced and extended, is now being applied to the task of any-to-cloud integration.
To delve into the enterprise application ‘black boxes’ of yore, Yaskin, now Founder and CTO with Queplex Corp., devised tools that connected to the data bases in question and abstracted business objects out of the resident data. A central element is what Yaskin calls a ‘persistent meta data server.’
Yaskin and company have expanded on the early tools, giving them an any-to-cloud integration twist. This week at the Salesforce.com Dreamforce conference, Queplex rolled out QueCloud on the AppExchange, which allows enterprises to integrate Salesforce with cloud and on-premise applications from vendors such as SAP, Oracle and NetSuite. It seems that a good view into enterprise application data is even more crucial now that real-time BI and cloud applications are becoming de rigueur.
Tools help as data integration project time is so often squandered on laborious data discovery stages, as Mark Brunelli notes in ”Experts reveal the top 5 data integration best practices” on SearchDataManagement.com. Visibility into data objects is a crucial first step in data integration, according to Yaskin of Queplex, who speaks with Brunelli in this article.
Slowly but surely, SOA has become an accepted way for enterprises to do software. There were many reasons for uptake to lag, not the least of which was that it was hard work to form software into manageable services. SOA services are still a work in progress, but they have become an accepted methodology. Continued »
A lot of the news in Service-Oriented Architecture now surfaces via blogs and Twitter. Long years after its inception, SOA still seems to generate controversy, although most people would agree that the controversy should not be overblown. Today we take a random look at a few notes afloat in the swirling winds of SOA on the Web. Continued »
By Jack Vaughan
How does cloud computing change development strategies for integration? The answer to the question is still a work in progress. A guide, however, may be found in Force.com. SalesForce.com was perhaps the earliest cloud player, building-out its whole company as a Software-as-a-Service offering, and launching one of the first Platform-as-a-Service (PaaS) offerings in the form of Force.com.
While SalesForce.com has fairly recently expanded its cloud portfolio to support open source oriented software in the forms of the Java Spring and Ruby-on-Rails frameworks, Force.com, with its proprietary Apex language, represents its flagship offering.
A good window into building cloud application integrations takes the form of a recent book: Development with the Force.com Platform: Second Edition, by Jason Ouellette. SearchSOA.com spoke with Ouellette at the time of the release of the first edition of the book for a podcast entitled ”Developing in the cloud with Force.com PaaS.” The story focuses on Apex as a language for writing business logic in a multitenancy setting.
We spoke with Ouellette again recently on the release of the second edition of his book. As can be expected in high technology, a lot has changed in the two years since the first edition. Ouellette said the Force.com platform has been improved in terms of JSON and REST API support; social media support in the form of Chatter components, feeds and APIs; and Batch Apex support added since the first edition.
SalesForce.com pioneered multitenant cloud computing, and, as such, had to solve some resource issues. SalesForce.com set governor limits to ensure fair treatment of applications from different customers. The number of records that can be queried at one time, the amount of memory used by code, the size of messages sent between Force.com and external hosts – all these matters are ”governed.”
Some individuals have likened aspects of cloud computing architecture to architectures of mainframe days. Certainly the governor limits discussed here recall the golden ears of batch computing. With Batch Apex, Ouellete told us, Force.com allows you to keep long-running data-intensive processing tasks within the Force.com platform.
Related Force.com information
Principle 73 in Alan Davis’ 201 Principles of Software Development discusses the need for loose coupling of software components. This is a ”known unknown” that bears repeating. Services composition remains a bit of a black art, and the key to successful application integration. Continued »
SOA has had at times a tough road to hoe, but it has survived and now with cloud computing architecture looming as the next big paradigm shift, SOA services stand out more than ever as the best path. Continued »
Are OSGi and Jigsaw at odds? The teacup tempest opens a view on a larger issue – that of component coupling. The Java controversy of late pits full OSGi modularity versus Jigsaw’s “simpler” approach. But, what is key perhaps is where the proper level of modularity lies for any given set of components. Continued »
As cloud computing and mobile services grow, the potential cost of poor performance becomes a greater issue. Yet, testing of newly integrated cloud services is just getting off the ground. A recent partnership between cloud computing provider RightScale and European load testing and performance-monitoring house Apica looks to address the issue. Continued »