SnapLogic Partners with 3Scale and Restlet for API Management

Mike Vizard
Slide Show

Top Trends Driving the Data Center in 2015

In another sign that API management is becoming a feature of larger integration frameworks, SnapLogic has announced it has partnered with both 3Scale and Restlet to embed API management inside the SnapLogic Elastic Integration Platform that is invoked as a cloud service.

Darren Cunningham, vice president of marketing for SnapLogic, says rather than build out its own API management platform, SnapLogic is opting to partner with third parties to provide access to that functionality. Because of that open approach, Cunningham says it’s probable that over time SnapLogic will support multiple API management frameworks.

While the SnapLogic core integration platform-as-a-service (iPaaS) engine resides in the cloud, the data integration process itself can be executed on premise or in the cloud using Snaps components and Snaps connectors. Cunningham says that approach is in keeping with 3Scale and Restlet, which both support different forms of hybrid approaches to API management.

While the API economy as a whole is apparently flourishing, there continues to be a debate emerging on both where API management should be executed and who in the IT organization should manage it. Some argue that API management is better provided in the cloud as a shared central resource, while others say that for performance and security reasons it should be primarily provided on premise. Over time, it’s likely that API management, much like data integration in the age of the hybrid cloud, will become federated.

Less clear is what part of the process the IT organization will manage. Given the fact that APIs are primarily created by developers, most of the management functions associated with those APIs have remained in the hands of developers. At the same time, however, as DevOps as a whole becomes more integrated, more responsibility for API management is moving into the hands of the IT operations teams that also typically manage data integration.

Regardless of the ultimate outcome, the one thing that is for certain is that going forward there will be a lot more of those APIs to manage.

Add Comment      Leave a comment on this blog post
Jun 30, 2015 10:09 AM Craig Oda Craig Oda  says:
Mike, wonderful article. I consult with Restlet, but I can't speak officially for them. You have a great idea about the changing role of the IT group as it relates to API management. I agree that the DevOps trends are accelerating the change. My personal view is that there are different jobs in API management: 1) API design, which is probably going to be done by developers 2) API development, which is done by development 3) API publishing, which may be managed by the IT group 4) API consumption, which could be in the realm of developers or data scientists or IT Just as an example, Restlet's APISpark allows publishing of data from a Google Sheet as a REST API with no programming. Thanks for taking the time to write your article. Reply
Jul 1, 2015 8:22 AM Greg Gamp Greg Gamp  says:
The world of API is getting more complex. Development and IT/Ops both play critical parts of an API lifecycle but more and more I see APIs evolving into core products managed and controlled the same as any other service or product. Conversations around how to acquire new customers / partners and monetization strategies expand the scope to include Market, Product Management, Business Development and Sales in the API conversation. Reply
Jul 2, 2015 10:31 AM Craig Oda Craig Oda  says: in response to Greg Gamp
Greg, are you the same Greg Gamp from Mashery? Would love to get more of your insights on where API management is located in an organization. As the author of the article points out, there's a movement from developers to IT for some components. However, you raise a great new point about the involvement of marketing, product management, business development and sales. Just as an example, I used to work as a "developer relations" consultant for both small and also very large tech companies. The budget was heavily skewed toward marketing groups. Most developer groups were interested and understood the value, but it was really the marketing groups that had the resources to make things happen. If the API is freely available, I wonder if it will be classified as a form of marketing in tech companies. Would be awesome to hear your thoughts. Reply

Post a comment





(Maximum characters: 1200). You have 1200 characters left.



Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.