July 2009
S M T W T F S
« May    
 1234
567891011
12131415161718
19202122232425
262728293031  

Applications

Thoughts on Open Source, Data Services, and Integration

SnapLogic 2.1 Enhancements

Posted 19 May, 2009 by Mike Pittaro in SnapLogic

No Comments

SnapLogic 2.1 is now available as a Beta release, and we encourage everyone to download and test it out.

The most visible change in this release is a complete reorganization of the SnapLogic Designer, to improve navigation and editing of transformation resources and pipelines, The new implementation uses a tree control that improved navigation for larger repositories, and an improved search capability. The available editing area is is now much larger, and the pipeline canvas now supports ’snap to grid’ capability.

2.1 Designer

Behind the scenes, there are quite a few improvements as well. We have enhanced the change detection in the server and designer, to simplify development and maintenance. When changes are made, the Designer now highlights the affected transformation resources in any affected pipelines, and allows viewing or automatic application of the changes to the pipeline.

The change detection is intelligent, and will only highlight relevant differences in view, parameter, and pass through settings. A popup provides detailed information about the changes, and allows the changes to be automatically applied to the affected pipeline.

2.1 Change Detection 2.1 Differences Dialog

Other improvements include help links from the general properties page directly to the documentation, support for duplicating transformation resources across servers, better management of multiple servers and runtime statistics directly in the Designer.

2.1 Runtime Statistics

As always, the installer images for Linux and Windows make installation painless, and take care of all the dependencies. The SalesForce.com, NetSuite, and SugarCRM extensions have all been updated for 2.1 compatibility, and the Windows version now runs as a full windows service.

Trackback URL :   http://blog.snaplogic.org/wp-trackback.php?p=273

SaaS integration versus integration as SaaS

Posted 25 March, 2009 by Mike Pittaro in Integration, SaaS

No Comments

Loraine Lawson has an interesting post over at IT Business Edge that highlights a recent Forrester Research study on the Future of Software as a Service Technologies. In the study, Forrester predicts minimal success for BI and Integration delivered as SaaS.

This news is no surprise to me.

Back in late 2007, Goldman Sachs released "Getting SaaS savvy - successful investing in on-demand", a research report on SaaS from an investment perspective. (There’s a summary of the Goldman report at SandHill.com). Goldman used 10 criteria to assess applications and determine whether there are well suited for a SaaS model (and potential investment) . Among those, the amount of integration needed was a key criteria. BI and data warehousing fared poorly. Integration on demand was not included in the report, but using the same criteria, it would not have been done well either.

This news isn’t "bad news for SnapLogic" either. As a software vendor, we have always believed the customer should be able to control their deployment, so SnapLogic runs portably on multiple platforms, virtual machines, and Amazon Web Services.

There’s definitely ambiguity around the term ‘SaaS integration’. Integrating on-demand applications is not the same as on-demand integration; there are big differences between the two.

The decision on where to run the integration process should involve the location of the data, security constraints, and the customers preference.

If the bulk of the data is already on premises, then integrate by pulling the necessary SaaS data on-premises. Security wise, this approach doesn’t introduce major new issues related to the data.

If the bulk of the data is SaaS, then a hosted or on-demand approach to integration may be more appropriate. Security wise, it may not be possible to send on-premises data out, and that has to be taken into consideration as well.

One size does not fit all in data integration; there are too many changes afoot in the IT landscape, and everyone need to have options.

Trackback URL :   http://blog.snaplogic.org/wp-trackback.php?p=263

Data Integration : Beyond the boundaries of the individual enterprise

Posted 24 March, 2009 by Mike Pittaro in Enterprise 2.0, Integration, REST Web Services, SaaS

No Comments

Gartner has released their 2009 Cool Vendors in Data Management and Integration report, and here at SnapLogic we’re thrilled to be named as one of the innovative vendors.

In the report, Gartner notes the expansion of data integration requirements to "encompass data beyond the boundaries of individual enterprises". One of their recommendations is to:

Investigate data integration technologies that can unify data residing in applications both inside and outside an enterprise’s firewall, in order to address alternative models for adopting business applications (such as SaaS) with flexible, yet cost-effective, approaches to data management.

Data integration has always been a complex problem. There are some good reasons why, including identifying and mapping data, defining the business rules behind transformations, managing data and metadata, and the fundamental nature of a process that crosses organizational and functional boundaries.

Changing requirements have always contributed to integration complexity. However, the current wave of industry changes is more fundamental; not only are we crossing organizational and functional boundaries, we now are crossing the enterprise boundary as well. Once you cross the enterprise boundary, you’re in the realm of cloud computing, with all its opportunities and challenges.

The cloud computing movement has put the core IT landscape itself in flux. These changes to the IT landscape are having a direct impact on data integration is three ways :

Expanded data sources

Adding to the complexity of what was once a purely on-premises function using internal data sources, we now have web data sources and data from SaaS applications to contend with.

Data integration has traditionally focused on databases and files, since that is where the bulk of the data lived. Applications were built on databases, so as long as you could ‘get to the database layer through the back door’, integration was possible.

SaaS applications change that assumption. Although still built on databases, the database ‘back door’ is no longer an option. Access is through defined API’s (usually SOAP Web Services based), replacing generic database connectivity with a need for an interface that understands the application and it’s internal structure.

Web data sources add another variation. Direct database access is usually not an option (and even if it is, the database may not even be relational.) However, the interface is typically REST, and still requires some knowledge of the application and its internal structure to use.

The last twist is the sheer number of SaaS and web applications to connect to. As of today, SaaS Showplace lists 950 applications, and Programmable Web lists 1200 API’s, which is a large set of possible data sources that might need to be integrated.

New consumers for data

As web and mobile technology influences the enterprise, the way data is generated and consumed is also changing.

In data integration, the traditional target for data has been a persistent database, usually a data warehouse or operational data store. That data has then been used for business intelligence, reporting, and analysis.

Although this model will continue, the need to provide data on demand, in the form of data services, is now a requirement. Consuming external data as a service, from free and commercial sources, is already common in the form of syndicated feeds. The concepts behind mashup applications, which combine data from multiple sources, are being used in lightweight and situational applications. These same concepts of multiple data sources and data services are now being applied to internal data as well.

New deployment models

Data integration has traditionally dealt with on-premises data, with some external reference data mixed in. The effect was an integration model influenced by the assumptions that most data would be local, and integration would be centralized.

The cloud movement challenges these assumptions for integration. The data sources are becoming a mixture of on-premises and remote data, with SaaS and web in the mix. The delivery is no longer to a fixed target; it can now be a mixture of SaaS, local targets, and data service endpoints. It’s likely that a mixture of these will be required in most organizations.

The shifts in data sources and data consumers have a direct impact on the way integration software is deployed. Integration software may need to be local, to enable access to on-premises applications and database. It may need to be remote, to provide a data services layer for one or more applications without service interfaces. It may need to be hosted, either in a data center or on a cloud platform, to take advantage of less expensive resources. The actual deployment model will be determined by the capabilities needed, not constrained by invalid assumptions.


The data integration landscape is changing, and that change is driven by fundamental shifts is the locations and types of data, and how the data is used. The core functions of data integration haven’t changed much, but the neighborhood we live in sure has.

Trackback URL :   http://blog.snaplogic.org/wp-trackback.php?p=255

JumpBox for SnapLogic

Posted 17 March, 2009 by Mike Pittaro in SnapLogic, SugarCRM

No Comments

The JumpBox team have released a new JumpBox for SnapLogic.

JumpBox simplifies server software deployment by providing pre-configured packages for software applications, which can be deployed on multiple virtualization and cloud platforms. Since we began SnapLogic, we have always believed that users should be able control their own deployments of software, and JumpBox is another great example of that flexibility.

JumpBox adds support for Parallels, Microsoft Virtual PC, Virtual Iron, and others to the existing SnapLogic platform matrix, and also simplifies configuring SnapLogic on our existing platforms, like Amazon Web Services.

You can also run an online trial directly from the JumpBox site without downloading or installing anything.

The JumpBox team also created a great example of using SnapLogic to check contacts in SugarCRM against the Specially Designated Nationals (SDN) list published by the Office of Foreign Assets Control.

Trackback URL :   http://blog.snaplogic.org/wp-trackback.php?p=249

On The Demise of W.S. SOA

Posted 24 January, 2009 by Mike Pittaro in Enterprise 2.0, Web Service Architectures

No Comments

The Burton Group have announced the unfortunate demise of SOA.

We have planned a memorial service event for Service Oriented Architecture, who met its demise on January 1, 2009.

For anyone confused, this announcement appears to be for W.S SOA. His Restful Cousin, who sometimes goes by the nickname WOA, is alive and well.

Trackback URL :   http://blog.snaplogic.org/wp-trackback.php?p=244

« Previous