Concerns Regarding the State of Enterprise Integration Today

DZone 's Guide to

Concerns Regarding the State of Enterprise Integration Today

Complexity, extensibility, and security.

· Integration Zone ·
Free Resource

We spoke to 20 executives in 16 companies to understand any concerns they have regarding enterprise integration.

Specifically, 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 primary concerns around enterprise integration is explosive complexity and extensibility

Here's what they told us specifically:

    1. People don’t understand loose coupling. Bringing integration back home can add latency. Not sticking to standards, patterns, architectures, making short-cuts is causing  us to return to the problems we were having in the previous decade.
    2. What is and is not possible in your organization. Moving to the cloud is not as easy as people think. Misconceptions about how easy it is to move to the cloud and to move from one cloud platform to the other. How long will it take versus the benefit to be received. Enterprise integration needs to be designed to be successful.
    3. Security. As you expose more data to the internet, security becomes more important. No single point of failure is acceptable. You need security across applications as well as physical.
    4. Like mobile, not everything that can be connected should be connected. Be mindful of opportunity and scale. Make sure you have the right tool for the job - pick the right API. Be mindful of security and scale.
    5. No, it’s a great time with the devices and platforms we have available.
    6. Standards being implemented by enterprise vendors to protect their garden rather than empowering their clients to integrate whatever they choose.
    7. At what point do we have so many pieces that the complexity overwhelms us? Need to make it real versus just adding complexity. What are the key things to build on for the next five to six years versus what’s not going to stand the test of time.
    8. More open networks. Closed networks prevent access to all services. On the internet, people have access to many services. Many people don’t know what they can achieve replacing legacy systems (i.e. MS Outlook) with solutions on the web where you need a browser and nothing else. More and more cloud APIs.
    9. Explosive growth in different areas of technology - containers, orchestration layers, many different applications all with different APIs. Enterprise IT staff want the flexibility to support but also manage the risk of all this stuff as soon as it becomes part of the enterprise. Who’s responsible for backup and maintenance.
    10. I have hope for where it’s going. Seeing business benefits like improved customer experience. Doing integration tied to end business results. Comes back to complexity and extensibility. Microservices are hot today but we had an SOA five to 10 years ago - you need to scope the granularity to make sure it’s not too small. It can be tougher to integrate.
    11. A lot of people are following the same message of performance, scale and efficiency. You can be 85% more efficient with data. Only send what’s needed by understanding the data. The network is already overloaded. Be more conscientious about what you are, and are not, sending.
    12. We still need to be more connected and it’s not happening as quickly as it needs to. More apps need to be built in an open way. All integration should happen seamlessly via APIs.
    13. Need to evolve from traditional systems in place.
    14. Possibility of a “snap-back” effect. From siloed to multiple tools and utilities that might negatively affect openness and creativity.

Do you share these concerns regarding enterprise integration?

Do you have others that weren’t mentioned here?

api development ,enterprise integration

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}