Unlocking enterprise agility in the API economy

Elsewhere, Coca-Cola has combined its global systems using application programming facades, allowing delivery faster and less expensive and improved multi-functional cooperation. Uber moved to microscopic services using API gates, allowing independent scaling and rapid publication across the markets.

In each case, the network had to evolve from being fixed, connected to the dynamic, programmed, consuming and consuming. “The API’s first infrastructure is naturally proportional to how IT teams work today,” Purkayastha says. “Constant integration and continuous delivery/publishing (CI/CD) pipelines and tools of service coincidence. This reduces friction and speeds up the speed of companies that can launch new services.”

Run the connection upon request

Tatta Communications has published a Fabric Network- Programmed platform that uses application programming facades to allow institutions systems to request and control the network resources dynamically-to help the Global Software Company as a SAAS to update how to manage the network capacity in response to the actual work needs. Since the company has expanded its digital services all over the world, it needs a more flexible and effective way to align the performance of the network with unexpected traffic and high user requirements. With the Tata platform, the company’s operations teams managed to automatically expand the domain range in the main areas of peak performance, during highly influential events such as global program versions. Speed ​​to reduce it by simply request normalization, and avoid unnecessary costs.

In another scenario, when the Saas provider needs to operate large -scale data operations between its American centers and Asia, the network has been replaced programming in less than an hour; A process previously required weeks of planning and savings. Purkayastha says: “What we have presented was not just the width of the frequency range. Their teams’ ability to control was,” Purkayastha says. “By integrating our network textile application programming facades in their workflow, we have provided them with a network that responds to their speed.”

Burns in front of the transformation – and how to overcome it

The conversion of the network’s infrastructure is not a small task. Many institutions still rely on the replacement of the old MPLS (MPLS) stickers (MPLS) and the widespread network operations (WAN). These solid environments are manually managed, and are often not compatible with modern application programming facades or automation frameworks. As with any institution, barriers can be technical and internal, and old devices may not support programmed facades. Institutions are often horrific, which means that networks are managed separately to work flows and Devops.

Moreover, CIOS faces rapid pressure on rapid returns and may not remain in the company for a long time to oversee the process and results, making it difficult to push for the long -term network update strategies. “It is often easier to treat low fruits rather than go after transformation because decision makers may not be present to see the shift beating life,” Purkayastha says.

But the reforms or rapid solutions may not result in the desired results; There is a need to shift instead. Purkayastha says: “The institutions have historically built their networks for stability, not the light movement,” Purkayastha says. “But now, the same hardness becomes the bottle of the bottle when the applications, users and work burdens are distributed across cloud sites, edge and distant.”