The Future of Enterprise Integration

DZone 's Guide to

The Future of Enterprise Integration

APIs and the Cloud democratize data.

· Integration Zone ·
Free Resource

We spoke to 20 executives in 16 companies to get their perspective on the future of enterprise integration and where the greatest opportunities lie.

Here’s who we spoke to:

Adam Fingerman, Chief Experience Officer, ArcTouch | Jon Gelsey, CEO, Auth0 | Nishant Patel, CTO, and Matthew Baier, COO, Built.io |Tyson Whitten, API Management Product Marketing, CA Technologies | Andrew Warfield, CTO and Co-Founder, Coho Data | Zeev Avidan, V.P. Product Management, OpenLegacy | Mike Han, V.P. Operations, Liferay | Uri Sarid, CTO, Conor Curlett, Principal Architect, MuleSoft | Gabe Stanek, Director of Field Engineering, Neo Technology | Florent Solt, CTO, Netvibes | Sean Bowen, CEO, Push Technology | Jon Bock, Vice President Products, Snowflake Computing | James Jinnette, Director of Information Technology, unidentified CRO | Suchit Bachalli, President, Unilog |Asanka Abeysinghe, V.P. Solutions Architecture, WSO2 |  Phil Manfredi, Aaron Sandeen and Kiran Chinnagangannagari, Co-Founders, Zuggand

The future of enterprise integration appears to be centered around APIs and the ease of accessibility they promise in the cloud - whether its robustness or steady accessibility. 

Here’s what they told us:

    1. More standardization. The platform nature of integration and Cloud support. Performance of a lot of transactions - scaling containerization. Most domain/data models are becoming more standardized - healthcare and insurance are leading the way. Organizations in the same domains can communicate in the same protocol with security thus providing smoother integration.
    2. APIs help provide information and make it easily accessible without customized pipes. Easy transfer of information with minimum customization. You can use as much or as little as you like - like a Chinese buffet. More efficient as long as everyone is using.
    3. Very clear APIs are the way forward. Monetizing APIs. Two modes: robust and steady; short, fast and agile to meet market needs. Organizations are realizing the opportunities and management is pressuring IT. See what customer-facing products are like and want more for the enterprise.
    4. Depends on the industry. Use cases differ by industry. Retailers need to integrate all of the backend with customer needs, coupons and loyalty. Airlines, healthcare, government all need to do something similar but slightly different based on customer expectations and needs. All of this will be beneficial for consumers. You must give everyone in the company a view of the data and the customer.
    5. 1000 different applications in early adopter industries. Will become global with more companies using more applications. We’ll have the internet of APIs. APIs are the fabric of the opportunity. Connect APIs to the capabilities of big data.
    6. Transform and improve every role in the organization with custom apps - salesperson, maintenance person, H.R., etc.
    7. Making the developer the new CIO by empowering them to build what they need with universal, aesthetically pleasing and simple solutions.
    8. Analytics used to be offline, now the technology enables it to be embedded in applications - smart application components. The capabilities will spread beyond big companies. Cloud has changed how customers can manage and access data. Making data accessible to more people. Democratization of data versus just available to Fortune 1000.
    9. Number of devices is evolving. Correlation between services, APIs and apps. Each app connects to data or service. This will expand as IoT expands. Also, the internal experience will be better because business users will demand the same experience they have as a consumer.
    10. Cloud with API integration. HR is able to connect a new employee with IT, email, team, services - even between companies that have partnerships (i.e. CRM, ERP).
    11. Provide a bridge without creating new APIs. No standards are evolving anytime soon. It took AWS 15 years. Something eventually wins. Support what’s most relevant to the client. Be flexible with regards to runtime and development tools while being scalable and secure.
    12. Launchpad helps provide orchestration fabric for a group of scalable services like caching. We can provide orchestration services so developers don’t have to think about so much. It’s easier to focus on vision of interaction - having the right information at the right place, at the right time, to the right person in the right format.
    13. IoT and mobile - IoT is probably one or two years away. Monitoring of devices. Sensors on cars - 10,000 cars taking 30 seconds. Need to add a diffusion layer - writing to a dashboard makes a subsegment.
    14. The customer experience will be drastically better than if the enterprise is not integrated.
    15. Two examples: 1) A layering approach in which legacy capabilities in older system mainframes and ERP systems integrate with 8,000 websites and omni channels to reach doctors around the world. Keep systems connected by building layers of APIs to reduce complexity. Layer above for approvals. Add a layer above that to enable websites to get information in real time. 2) Systems integration for a logistics firm with 15 different systems. Build a single conical API for one of the systems to which the other 14 systems can connect. The domain API becomes popular within the company. Employees have a more consistent approach to data. Self-service virality drives innovation and agility. Everyone dealing with invoices in a consistent way. Productization of APIs - provide the right documentation for APIs making it easier to get virality going. Everyone in the company can make changes easily and online.
    16. People know how to integrate data silos. Test a lot of different disciplines because there are a lot out there.

What’s your vision of the future for enterprise integration?

api, cloud, data, data + integration, enterprise integration

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}