Software AG: 2017 Predictions for Application Integration
February 13, 2017

“Integration is no longer your IT department’s problem; it is everyone’s problem," according to David Overos, Director of Product Marketing for Integration at Software AG. "With the IoT, APIs, blockchain and chatbots thrown into the mix, everyone needs to integrate with everything. And this is leading to companies who are partnering with integration vendors to ensure their success as they adopt these, and other disrupting technologies, in the future.”

The following are Software AG's predictions for Application Integration in 2017:

1. Specialists Not Required

Integration is becoming a pervasive problem across businesses, and that means integration tools will need to accommodate multiple user types along with traditional developers. Therefore integration vendors will need to provide tooling for ad hoc and non-technical developers as well as specialists, including graphical, low code solutions.

2. Microservices

Mature cutting-edge development teams experimented with microservices last year, but in 2017, mainstream organizations will take microservices architectures into production with real projects. To support these initiatives, integration vendors will go to market with microservices using important supporting technologies such as containers (Docker, Kubernetes, etc.).

3. IoT Integration Everywhere

The IoT is a buzz this year with talk of smarter "things" plus the increased use of edge computing for analytics. So, as more companies move into real IoT implementations, the role of integration as the broker of "thing" data will become fully realized. Data is only valuable if it gets delivered.

4. Integrating Integration with APIs

A flurry of recent acquisitions of major API management vendors, such as Tibco’s purchase of Mashery and Rogue Wave Software’s Akana buy, showed the world that APIs are part of a bigger market — integration. Companies now view API Management as an extension of integration — because that’s where they are developing their APIs. This is a clear indication that the IT community recognize the value of APIs for application integration, and this trend will continue to gain importance in 2017.

5. Rise of the Chatbots

Artificial Intelligence is everywhere these days, especially with the rise of chatbots and virtual assistants. But even the smartest chatbot can only provide intelligent responses if it has the right data to work with. We will see an increase in the need for bots to have timely data such as customer, product and service data to improve the virtual experience of customers.

6. Blockchain Integration

The financial sector is seeing an increase in the use of blockchain technology for fast and secure payments. And industry after industry is getting in line behind the banks to adopt blockchain as a way to track secure ledgers of transactions, from healthcare to manufacturing. Integration will be the key that ties these new initiatives into your business, adding new channels for secure and fast business.

Overos noted: “Now that data accessibility is more manageable through these integrated lightweight protocols, containers and robust APIs, it’s becoming increasingly crucial to turn the growing mountain of data from disparate sources and formats into consumable information and actionable insights. IT departments need to find a new way forward to support the enterprise infrastructure and maximize the potential benefits of having improved access to data.”

Author

Pete Goldin

The Latest

September 18, 2017

Web development and web design are intertwined in such a way that there is not one without the other — not anymore at least. The following outlines 5 benefits of collaboration ...

September 14, 2017

Mastering modern software development by building a "Modern Software Factory" is at the heart of business success in the digital economy, according to the results of a survey of over 1,200 IT leaders released today by CA Technologies ...

September 13, 2017

IT-Business convergence is needed to deliver continuous change, but many of the current tools add complexity and fail to merge the two, according to the Panaya 2017 State of Functional Testing Report ...

September 11, 2017

Application Program Interfaces (API’s) represent an effective way to build and manage mobile services. By using APIs — a set of routines, protocols and tools for building software applications — application developers no longer have to buy technology software or hardware. Instead, they can simply plug into a growing open ecosystem of API-driven services. It is simple to integrate, and saves time and money for new developers ...

September 07, 2017

More than a quarter of enterprises globally have not built, customized or virtualized any mobile apps in the last 12 months, according to the latest mobile app survey by Gartner ...

September 06, 2017

The number of malware breaches (to use a generic term) are rising in near exponential numbers and, unless there are radical changes, this is set to continue unabated. Most pundits agree with this forecast ...

September 01, 2017

DevOps encourages communication and collaboration between development and operations teams. Achieving greater synergies between the Dev and Ops teams doesn't happen overnight, but it is possible to fast track the process with the right technologies in place. One such technology is IT automation ...

August 29, 2017

Newly released data shows that distributed denial of service (DDoS) and web application attacks are on the rise once again, according to the Second Quarter, 2017 State of the Internet / Security Report released by Akamai Technologies ...

August 28, 2017

Organizations that are actively managing the quality of open source components flowing into production applications are realizing a 28 percent improvement in developer productivity, a 30 percent reduction in overall development costs, and a 48 percent increase in application quality, according to the 2017 State of the Software Supply Chain Report from Sonatype ...

August 24, 2017

Being able to deploy distinct code elements quickly, matched with the ability to deploy the next release version or the previous version, facilitates moving forward, even on failure. The small program unit minimizes the production impact upon failure — maybe only a few people experience the problem instead of a large set of application users when large code deployments go wrong. Besides implementing small code segments, there are two additional reasons why fail forward has proven successful: continuous integration and testing ...

Share this