5 Pillars of API Management | SlashdotMedia AdOps Asset Management

5 Pillars of API Management

Across industry sectors, the boundaries of the traditional enterprise are blurring, as organizations open up their on-premise data and application functionality to partner organizations, the Web, mobile apps, smart devices and the cloud. APIs (application programming interfaces) form the foundation of this new open enterprise, allowing enterprises to reuse their existing information assets across organizational boundaries.

A Guide to REST and API Design

In his 1966 book “The Psychology of Science,” American psychologist Abraham Maslow tackled the idea that those in the field of psychology needed to approach treatment from multiple perspectives, to take on new ideas, and not just continue using the same theories and techniques created by Freud and his followers so many years ago. Acknowledging that changing your point of view can be difficult, Maslow wrote “[I]t is tempting, if the only tool you have is a hammer, to treat everything like a nail.” We have all had this experience. We get so used to the way things have been done in the past, we sometimes don’t question the reasons for doing them.

A How-to Guide to OAuth & API Security

OAuth is an emerging Web standard for authorizing limited access to applications and data. It is designed so that users can grant restricted access to resources they own—such as pictures residing on a site like Flickr or SmugMug—to a third-party client like a photo printing site. In the past, it was common to ask the user to share their username and password with the client, a deceptively simple request masking unacceptable security risk. In contrast to this, OAuth promotes a least privilege model, allowing a user to grant limited access to their applications and data by issuing a token with limited capability.

What is a Process-Based Application?

Companies today need to move from a functional model to a process‐oriented model, allowing them to be more flexible and proactive to changes in their environment. Current information systems and processes rarely correspond to a transparent, cross border organization. On the contrary, these information systems replicate and reinforce the classical and functional organizational structure, where each business unit has its own applications and data silos. This of course leads to inefficiencies due to redundancy of data in different systems.

Develop a 1st Business Process Application with Bonita BPM 6

Whether you are wondering how BPMN can significantly improve the efficiency of your daily operations or whether you are wondering how to turn an existing process into an optimized dynamic application, this paper addresses these challenges through a concrete business example: the modeling and the automation of an employee leave management procedure. We have put ourselves in the shoes of a project team engaged in the development of its first BPMN implementation.

The example application is developed with Bonita BPM 6 Teamwork Subscription Edition. This paper also gives some pointers to develop it with Bonita BPM 6 Community Edition.

The Ultimate Guide to BPMN2

We realize that many people and organizations who could benefit from BPMN have yet to give it a try. It may be that you’ve been putting it off under the mistaken assumption that you need to be an expert to use BPMN. Or it may be because the standard itself, and many of the things written about BPMN, are bit unwieldy and hard to dissect.

Mitigating Mobile App Risk to Ensure Safe, Reliable Deployments

Driven by the trends of Bring Your Own Device (BYOD), Bring Your Own App (BYOA), and the consumerization of IT, the mobile device tsunami is inundating enterprises around the world. In many organizations IT is responding by giving employees unfettered access to these apps. But that can expose the organization to considerable risk.

SOLVING FOR “TOTAL COST” IN THE CLOUD

It’s a simple question: How much is it going to cost to move an application to the cloud? But the answer is not simple, and many businesses suffer costly surprises when they make the move.

This paper shows you how to calculate the total cost of migrating applications to the cloud, including obvious hardware costs as well as the human costs of managing apps in the cloud.

Have you factored in these costs?

• Training related to new skills, tools, and processes

• Server CPU, memory, storage, and monitoring

• VPN and direct connect fees

• Need for additional cloud administrators

• Cost of moving data to the cloud

2014 Gartner Magic Quadrant for Cloud-Enabled Managed Hosting, Europe

The "2014 Gartner Magic Quadrant for Cloud-Enabled Managed Hosting, Europe" is available now and there are some important insights that will inform your strategy for bringing cloud like consumption and provisioning attributes to the traditional managed hosting market.

Read the full report for an in-depth analysis of the European market for cloud-enabled managed hosting and the vendors to watch out for.

CloudHarmony CenturyLink Hyperscale Testing Report

The independent testing results are in, and CenturyLink Cloud’s Hyperscale cloud compute instances are the ones to beat for key performance measures and total cost of ownership. With the launch of our new Hyperscale server instances, we approached an independent analytics company, CloudHarmony, and asked them to conduct an extended performance test that compared CenturyLink Cloud Hyperscale servers to the best of breed equivalent servers offered by AWS & Rackspace. CloudHarmony is a well-respected shop that collects data from dozens of benchmarks & shares the results publicly for anyone to dissect.

After running a variety of benchmarks over a long period of time (to ensure that the test gave an accurate look over an extended window), they shared their findings with the world.

5 Pillars of API Management

Across industry sectors, the boundaries of the traditional enterprise are blurring, as organizations open up their on-premise data and application functionality to partner organizations, the Web, mobile apps, smart devices and the cloud. APIs (application programming interfaces) form the foundation of this new open enterprise, allowing enterprises to reuse their existing information assets across organizational boundaries.

A How-to Guide to OAuth & API Security

OAuth is an emerging Web standard for authorizing limited access to applications and data. It is designed so that users can grant restricted access to resources they own—such as pictures residing on a site like Flickr or SmugMug—to a third-party client like a photo printing site. In the past, it was common to ask the user to share their username and password with the client, a deceptively simple request masking unacceptable security risk. In contrast to this, OAuth promotes a least privilege model, allowing a user to grant limited access to their applications and data by issuing a token with limited capability.

Choosing the Right API Management Solution for the Enterprise User

The application programming interface (API) may be an old concept but it is one that is undergoing a transformation as, driven by mobile and cloud requirements, more and more organizations are opening their information assets to external developers.

Today, 75% of Twitter traffic and 65% of Salesforce.com traffic comes through APIs. But APIs are not just for the social Web. According to ProgrammableWeb.com, the number of open APIs being offered publicly over the Internet now exceeds 2000—up from just 32 in 2005. Opening APIs up to outside developers enables many technology start-ups to become platforms, by fostering developer communities tied to their core data or application resources. This translates into new reach (think Twitter’s rapid growth), revenue (think Salesforce.com’s AppExchange) or end user retention (think Facebook).

5 OAuth Essentials for API Access Control

OAuth puts the user in control of delegating access to an API. This allows one service to integrate with another service on behalf of that user. The same social Web providers who popularized the pattern of exposing an API to enable third-party developers to enrich their platforms were the first ones to apply such delegated authorization mechanisms. OAuth was defined in 2006, to standardize mechanisms of this kind.

Five Simple Strategies for Securing APIs

Since the early days of computing, developers have struggled to make applications communicate. Specialized protocols, such as COM+, CORBA, and even SOAP, emerged over the years, but none were sufficient to meet the need for scale, simplicity, and cross-language functionality.

APIs are the technology behind this approach. APIs allow developers to create an open architecture for sharing functionality and data between applications. APIs are like windows into an application—a direct conduit that leads straight into the core functionality and data residing in the heart of the app.