What Are Concerns With Integration and APIs?
There is a broad range of concerns around integration and APIs, with the most predominant being security, tools, and being business-centric.
Join the DZone community and get the full member experience.Join For Free
To gather insights on the state of integration, API design, and API management, we spoke with 19 executives who are familiar with integration and APIs and asked them, "What are your biggest concerns around integration today?"
Here's what they told us:
- Implementation level provides APIs and services to integrators while maintaining a certain level of service. We provide an API with documentation and developers figure out the most creative way to use the API rather than following best practices. You must be able to detect and isolate as soon as possible. Employ security around APIs to provide the best UX.
- Security. Developers need to ensure that their users can only access the data and services to which they're entitled. The traditional way to achieve that has been to implement complex access rules in the application backend – MongoDB Stitch takes care of this, letting developers configure rules using simple JSON documents.
- Lack of security is a big concern when it comes to API management and integration. By making its API available, an organization opens up the backend of its solutions or platforms for anyone to access and use. This creates security implications. Developers should spend enough time while building integration to keep users’ data safe. Fine-grained permissions are most desirable. Have the API source code checked by an expert to test whether it could be abused or misused by a malicious user? Think about what data gets exposed to apps/integrations built on top of their APIs.
- I think we’re at a point where we have a host of powerful and accessible tools to build the next generation of integrated systems, but we need to be mindful of the discipline it takes to use them well. A platform is only as good as the value it presents to a business, no matter how cool the technology is. We should design platforms that don’t shy away from hairy integration tasks, but also make it effortless to integrate with modern, standards-aligned systems.
- There’s more need for integration. The standardization already exists. Everyone opened interfaces. Now, with Swagger 2.0, we have a common way of talking. More opportunity than ever before. Need to be more business-centric than before. The only thing that can slow down the proliferation of APIs and integration are developers trying to write everything without focusing on putting business logic in the API. Buy versus build to ensure the acceleration of development.
- Don’t stick your head in the sand. This is a tremendous opportunity. Create a disruptive experience with APIs.
- Performance and reliability depend on the system we’re integrating with. We get blamed if the integration doesn’t work. SLA’s may be defined but they’re not easy to prove, and ultimately the customer doesn’t care who’s responsible, they just know their applications are not integrating.
What are your concerns around integration, API design, or API management at this time?
Here’s who we talked to:
- Murali Palanisamy, E.V.P., Chief Product Officer, AppViewX
- Kevin Fealey, Director of Automation and Integration Services, Aspect Security
- Max Mancini, VP of Ecosystem, Atlassian
- Shawn Ryan, V.P. Product Marketing, Digital as a Service, Axway
- Parthiv Patel, Technical Marketing Manager, Built.io
- Chaitanya Gupta, CTO, Flock
- Anwesa Chatterjee, Director of Product Marketing, Informatica Cloud
- Simon Peel, CMO, Jitterbit
- Keoki Andrus, VP of Products and Steve Bunch, Product Manager APIs and Integrations, Jive
- Rajesh Ganesan, Director of Product Management, ManageEngine
- Brooks Crichlow, Vice President, Product Marketing, MongoDB
- Derek Smith, CEO, Naveego
- Guillaume Lo Re, Senior Software Engineer, Netvibes
- Vikas Anand, V.P. Product Management and Strategy – Integration, Oracle
- Keshav Vasudevan, Product Marketing, SmartBear
- Kevin Bohan, Director of Product Marketing Manager, TIBCO
- Pete Chestna, Director of Developer Engagement, Veracode
- Milt Reder, V.P. of Engineering, Yet Analytics
Opinions expressed by DZone contributors are their own.