Apis built according to rest architectu standards are

This preview shows page 118 - 121 out of 162 pages.

REST stands for “representational state transfer.” APIs built according to REST architectural standards are stateless and offer a simpler alternative to some SOAP standards. For example, REST enables plain-text exchanges of data assets instead of using complex WSDL protocols. It also makes it possible to inherit security policies from an underlying transport mechanism. At a high level, these and other simplified approaches can deliver better performance and faster paths to develop, deploy, and triage.Finally, API management platforms have evolved to complement the core messaging, middleware, and service bus offerings from yesteryear. Vendors include new entrants and established players, including IBM, SAP, Oracle, Tibco, MuleSoft, Dell, Software AG, CA, Dell, and Apigee. Misconception:Project-based execution is cheaper and faster. I don’t have time to design products.Reality: With urgent projects, or those dependent upon tactical integrations, you may not be able to invest much design time up front. But understand that you will have to duplicate your efforts, A to Z, when you begin the next project. By spending some time on understanding cross-project requirements and designing for reuse, your costs—in both time and budget—become leveraged, and the value you create compounds over time. The goal is not to construct centralized, enterprise-wide controls and governors—rather, it is to create assets that can empower teams to drive accelerated time-to-value. Sure, there will be some stand-up cost. And the initial projects Tech Trends 2018: The symphonic enterprise116
will involve scoping, designing, and building different types of assets. Consider subsidizing those investments so that business owners and project sponsors don’t feel as though they are being taxed. Also, look for ways to reward teams for creating andconsuming APIs. Misconception:I don’t have the executive sponsorship I need to take on an API transformation. If I don’t sell it up high and secure a budget, it’s not going to work. Reality: You don’t have to take on a full-blown API transformation project immediately. Begin building a business case by completing a few small, low-cost projects that demonstrate the ROI around reuse of a common set of APIs. CIOs may be able to develop a proof point with as few as three APIs delivered across two or more projects (three is a manageable number to prove reuse ROI). Subsequent success with a few tightly scoped projects can then help lay the groundwork for business support and, eventually, executive sponsorship.API imperative117
LESSONS FROM THE FRONT LINESAT&T’s lean, mean API machineIn the last decade, AT&T embarked upon a se-ries of mergers, uniting several large companies. They resulted in an IT organization having to man-age more than 6,000 applications, as well as distinct operating and software development life cycle pro-cesses, each of which worked well in its own right.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture