InformationWeek "Age of API" November 2013

8/13/2019 InformationWeek "Age of API" November 2013

1/13

Next >>

NOVEMBER 2013

As web-based intits dawning on e

they need a more

API strategy >>

By Joe Masters Em

informationweek.com THE BUSINESS VALUE OF TECHNOLOGY

PLUS Beyond Wa

Three techs that d


2/13

Artificial intelligenceis infiltrating our ev-

eryday lives, whether we realize it or not. Its

powering smart systems and solving busi-

ness problems think about using machine

learning and big data to create new services

and enhance existing ones. In some domains,

AI systems are already more skilled than

humans, and in the coming years AI will re-

cast strategies across many industries, from

healthcare (AI systems are helping detect can-

cer now) to harnessing the power of crowds

to solve big problems (like gamers helping

with genome research). And in most cases, itwill all seemdead simple. The complexitys on

the back end. So how can typical companies

tap into the power of AI now? There are three

areas I think bear watching.

E-commerce and product recommenda-

tions:Amazon incorporates collaborative

filtering the first generation of online rec-

ommendations. Youre undoubtedly familiar

with these if you bought product A, you will

probably like product B pitches. However,this method has limitations, the biggest be-

ing that collaborative filtering works well only

for products driven by taste and bought in

large quantities; if you purchase lots of B.B.

King tracks and Elmore Leonard novels, Ama-

zon probably does pretty well at suggesting

new options. However, higher-priced items

or goods that arent bought in large quanti-

ties (and thus generate little interaction data)

arent conducive to being purchased by rec-

ommendations via collaborative filtering.

AI-powered second-generation recommen-

dations expand this reach to new product

areas, including ones that present the user

with constraints and needs while setting thefoundation for a knowledge-based struc-

ture. For example, someone could say he

wants a tablet that runs Android, offers 4G

LTE and costs less than $800. This also sets the

stage for long-tail recommendations: Now

you know a customer is an Android user and

values always-on, fast connectivity.

How to get an advantage: Retailers need

to get better at processing product databases

and extracting data from internal and exter-nal sources to gain superior knowledge about

products. Example classification and extrac-

tions, along with image an

tion, help you build better

ally work to pull in new in

Im seeing AI used to gathe

multiple data streams ac

sites, in order to recomm

products to consumers. In

must recommendation s

on statistical correlations

consumers are buying; th

deeper information sour

why, when, where, how

tantly, what customercessing data in new ways

account a deep understan

as gender, time of purcha

erences, amount of time

page, click trails all that

AI systems to help the bu

consumers preferences an

Vertical search:Vertica

search is gaining popula

travel and electronics tomore; its where a perso

a site such as IMDB or K

Beyond Watson: 3 Techs That Depend On AI LA R@

Previous Next

informationweek.com

practicalAnalysis

Sound Off

Want to raise your profile?InformationWeekis looking for

technology and business strategyexperts to write independent

and thought-provoking opinioncolumns for our site. Contactmanaging editor Shane ONeill

to learn more.
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


3/13

through a general engine like Google or Bing.

Vertical search uses semantics, text classi-

fication, feature extraction and advanced

big data analytics mixed with other AI algo-

rithms. Google is waking up to the threatand

lately has put a lot of effort behind vertical

search in an effort to deliver more relevant,

tailored results. However, vertical search

presents an opportunity to get an edge on

Google by incorporating human logic and

knowledge into specific verticals or apps. A

good example is Zite, an app that offers rel-

evant news articles by learning behavior. It

uses several AI technologies to make news

delivery much more intelligent than a simpleGoogle News feed.

How to get an advantage: Consider mak-

ing vertical search pools plentiful, narrowly

focused, and well-stocked with content. Deep

verticals can cooperate and solve problems

without a loss of precision.

Virtual assistants:The app explosion that

began when smartphones hit the market

isnt slowing. Now, the trick is standing out

via intelligent apps that go beyond just per-

forming basic commands, becoming more

intelligent and seeking to be more predictive

of end-user behavior. While Siri and Google

Now arent quite there yet, the next-gen vir-

tual assistant will not only deliver meaningful

information but will do so in a curated, predi-gested, presentable way that creates a seam-

less user experience. The big dogs are racing

to build this next-generation virtual assis-

tant. Last month Apple acquired Cue, a vir-

tual assistant platform, in a move seen as an

indication that its trying to make Siri smarter,

more predictive, and more interactive. While

its hard to imagine the current iterations of

Siri or Google Now being a staple in most

peoples everyday lives, we as humans willadapt and come to expect on-target recom-

mendations and intelligent answers.

How to get an advant

prises wont be building

assistants anytime soon,

to begin to rely on virtua

become able to provide re

ful information. Watch the

as you design APIs, for exa

the goal of developing lon

lationships with customer

which they interact.

Overall, the smarter an

the more predictive it can

better it performs for the e

less likely it is to get deletneeds more space for cat vi

ities continue to expand, w

systems that actually unde

human behavior. Yes, to g

to jump a lot of technolog

ness incredible amounts of

But make no mistake: Mac

artificial intelligence will

exciting, compelling produ

Lars Hard is CTO and founder of Exp

[email protected].

The smarter an app is, the more

predictive it can be, the better it

performs and the less likely it

is to get deleted when someone

needs more space for cat videos.

Previous Next

informationweek.com

practicalAnalysis


4/13

informationweek.com

As web-based integration wiits dawning on enterprises that th

a more sophisticated API strat

APIs arent used by justmobile applic

opers, though mobility is one reason

denly waking up to the possibilities o

lowly application programming interface. T

critical for connecting your business with papliers, and cloud providers, particularly if you

software-as-a-service. Is software-defined ne

your future? Arista, Cisco, Enterasys, Juniper

networking vendors expose rich APIs to autom

operations. Amazon.com built its business o

data and functionality through interfaces that

a dime, extend outside the company.

There must be a business case for developin

well discuss what they can do for you. But IT o

also need a back-end plan: How will you expose

Which protocols and middleware should you su

can you share APIs with outside parties secure

By Joe Masters Emison @JoeEmis

NextPrevious


5/13

informationweek.com

will you guarantee performance?

The first thing your organizat ion needs to

do is formalize API management and think

about security. Some shops are already mak-

ing headway; well discuss programs by AT&T

and Bechtel. Cloud providers and standards

bodies are in the thick of planning Randy

Bias, CEO of Cloudscaling, and Boris Renski,

CMO and co-founder of Mirantis, recently

debatedthe wisdom, or lack thereof, of focus-

ing on those Amazon APIs for the OpenStack

project. Well dig into how APIs got to be the

center of the software universe.

On The Rise

Like most IT movements, necessity was the

mother of API invention. Development pio-neer Edsger Dijkstra dubbed it the software

crisis as hardware gets more powerful

and technology more intrinsic to business,

development complexity increases in lock-

step. The result: late, over-budget, unman-

ageable software of questionable quality.

In response, programmers started breaking

massive blocks of code into component-

based chunks, from Unixs pipes to Corba

(Common Object Request Broker Architec-

ture) to service-oriented architectures. Across

each era, the goal was the same: to keep units

of code small so that developers could find

errors and do updates more quickly and eas-

ily. Despite some pain Corba and the strict

SOAP standard, for example, are complex and

costly to implement enterprises generally

came to agree that component-based coding

is an improvement over monolithic software

development.

Then some thi ng unexpecte d hap pened:

Consumer-facing Web companies saw the

potential to scale their businesses to tens

of millions and then hundreds of millions of

users, but they needed ways to ramp up

quickly. One popular met

yourself a platform and

third-party developers to

site. In doing so, they used

had to that point been u

scribe a portion of the larg

software development kits

software vendors made a

developers. But web comp

ter, Facebook, and Netflix

in being gatekeepers. Ins

and freely released, simp

Web APIs; this helped th

AGE OF THE A

Get This AndAll Our Reports

Our full report on mobile com-

merce is free with registration.This report includes 63pages of

action-oriented analysis, packed

with 53charts.

What youll find:

> What 1,182 respondents seeas the No. 1 mobile commerce

challenge

> Key techs required for mobile

commerce success

DownloadDownload

Previous Next

51%

27%

22%

Do You Support An Open API Program?

Data: InformationWeek and Mobile Commerce World Mobile Commerce Surveyof 138 telecommunications professio

with their organizations mobile commerce strategies, March 2013

Dont know

No

Yes
http://prevpage/http://prevpage/


6/13

quickly via strong developer support.

However, these Web companies soon found

that their APIs were useful to a fairly small set

of developers, not to some long tail commu-

nity that would continually drive new value.

So they started shifting their focus, shutting

down public access to pieces of their APIs.

Netflix no longer issues public developer API

keys,and Twitter is placing greater limits on its

public API.The API focus has shifted to favored

partners and internal and contract developers.

Its a simple cost-benefit calculation: They had

a bunch of people who werent adding much

revenue or other value but who required sup-

port. More important, those developers were

hitting their public APIs, chewing up lots of

bandwidth, and sometimes exposing valuabledata. Time to tap the brakes.

Meanwhile, enterprises started wondering

how they would manage to connect their

Web services environments (mostly SOAP and

XML-RPC) to increasingly popular Internet-

based SaaS products such as Salesforce.com,

says Dimitri Sirota, senior VP of business unit

strategy for CA Technologies and co-founder

of API management firm Layer 7. In particular,

integrations using SOAP were excruciatingly

painful and expensive to build, yet not par-

ticularly reusable, making the development

pipeline long and organizations much less

agile than they wanted to be. The APIs pio-

neered by consumer-facing Web companies

seemed to be excellent, flexible models for

enterprises to build abstraction layers among

their various internal and external systems.

Certainly, thats the lesson big-enterprise CIOs

(those with foresight, at

ing from nimble startups b

nesses on APIs and displa

based development techn

The result: a new age ba

web API, usually a RESTfu

HTTP/HTTPS that returns t

JSON (JavaScript Object N

contrast to clunky, less-us

such as SOAP and XML.

Key reasons for embracin

SOAP/XML include the foll

>> Developer ease of

ity of REST/JSON cut deve

streamlining everything fro

to programming to debug

>> Faster transport.As use rises, the verbosity of

to slow responses, and th

experience. And that may m

>> Easier upgrades.The

tice is to put each function

whereas SOAP generally h

multiple functions, which

and enhancing SOAP more

There are st ill some com

use SOAP/XML, and there

SOAP APIs in the wild. At

2,098 of the 8,584 APIs list

informationweek.com

AGE OF THE APrevious Next

1. JSON:JavaScript Object Notationworks well with HTML5 mobile applications.

Its more data-efficient than XML and easier

to manipulate for client code.

2. Single Page Architecture Frame-works:A new technique for building Web-based applications that align more directly

with app development paradigms. Provides

better alignment between Web and app

development frameworks, which increases

reuse.

3. OAuth:Widely used standard authen-tication protocol provides secure login for

mobile applications without sharing username and password combinations with

applications; developers gain libraries and

best practices.

Data: 3scale

3 Critical API Techs
http://prevpage/http://prevpage/


7/13

informationweek.com

bleWebare SOAP-based. Many of them are

likely older code, but the strictness of SOAP

allows for much better automated validation

than REST does. What do we mean by strict-

ness? For example, a strongly typed SOAP API

contains a complete definition of its input and

output messages, and SOAP has well-defined

transport protocols. These strictures at least

in theory support the use of SOAP/XML

APIs for some greenfield uses. In particular, if

you need a strictly defined one-to-one con-

nection between two applications, where be-

ing able to validate complex input and output

is essential, SOAP may be worth the effort.

Still, keep an eye on JSON. Rob Zazueta, direc-

tor of platform strategy at API management

firm Mashery, says the spec will be extended toprovide the structural benefits of SOAP. He cites

JSON projects such as Siren(Structured Inter-

face for Representing Entities),Collection+JSON,

and GeoJSONas offering some of the benefits

of SOAP without all of the negatives.

One thing is certain: The preferred techno-

logical choices for APIs are still evolving, and

anyone who locks into todays technology will

eventually miss out on advantages.

Fortunately, as well discuss, specific tech-

nological choices are really of secondary

concern. Its fine to keep changing techs in

play. What matters much more is making life

easy and productive for the developers and

other users of your APIs.

Popularity Plus

In the past few years weve watched APIs go

from Hey, this seems like a good idea to Ive

got a fever, and the only p

APIs! There are two reason

surge: business partners an

In his Software Is Eating

Marc Andreessen argued

either start as software co

Netflix), become software

Previous Next

2013 2012

How Do You Integrate Various Cloud And SaaS Applications?

Custom coding directly to our internal system using each vendors API

Leverage an internal integration platform

Leverage a traditional VAN for data integration

Leverage a cloud-based integration platform

Other

Dont integrate; users have separate accounts for each provider

Dont know

Data: InformationWeek State of Cloud Computing Surveyof 176 business technology professionals in February 2013

at organizations with 50 or more employees using cloud services

11%

14%

11%10%

10%

9%

3%

5%

33%

NA

12%

27%

AGE OF THE A


8/13

informationweek.com

cast, Wal-Mart) or get crushed by software

companies (Borders, Kodak). And as each sur-

vivor moves deeper into a digital existence,

it becomes more and more important for all

aspects of that company, especially its criti-

cal partner relationships, to be digitally con-

nected. Thats driving API development. Each

individual partnership with big enterprise

integration vendors using SOAP cost millions

of dollars, took far too long, and didnt scale,

says Steven Willmott, CEO at API manage-

ment firm 3scale. With a RESTful API, it was

suddenly feasible to work with 1,000 partners:

Heres my endpoint; integrate with it.

And when every one of those partners

wants some level of programmatic direct ac-

cess to your internal systems, you had betterhave a strategy that scales.

Just as business-partner benefits were ad-

vancing Web APIs over SOAP and XML, the

rise of mobility gave them a turbo boost.

We understood the desktop Web demand

pattern HTML, HTTP, maybe some person-

alization but mobile apps dont behave

like browsers, says Sam Ramji, VP of strategy

at app and API infrastructure firm Apigee.

Mobile apps are much chattier than desktop

web applications, sending 20 to 30 small mes-

sages. They require a different strategy.

Its not just a matter of performance.

Lighter-weight APIs use fewer valuable mo-

bile device hardware (CPU, memory) and bat-

tery resources. An excellent blog post from

AT&T Researchbreaks down how IT organiza-

tions must design apps to be energy-efficient

(architected with the power-up/power-down

requirements of the radio). And software de-veloper Drew Crawford has written acom-

prehensive breakdownof why mobile Web

app performance will be quite slow for the

foreseeable future.

All of those points lead to the inescapable

conclusion that SOAP and XML are too cum-

bersome for efficient data transfer to and

from mobile devices. And that bodes well for

the further rise of REST/JSON web APIs.

Before we get into best practices for inte-

grating APIs, lets look at some examples of

successful business uses.

AT&Ts API programs le

tomate voice and video c

sages and help them acce

nologies, such as speech

APIs generate more than

month, and this efforts ju

its enterprise API prog

over a month ago. The com

challengeas evolving fro

products tohelping enterp

atefinished products.

Meanwhile, Bechtel, the

tion and engineering co

built APIs to connect worke

incredibly diverse busine

For example, its connect

US with on-site contractorsure deliveries are on time

cations. A quick picture fro

and contractors can get o

while cost- and quality-co

pare what was promised w

Christian Reilly, manage

agement at Bechtel, sees

strategy as helping it succee

environment, where som

built slowly (and some ol

stay), but others have to be

A few other examples


With a RESTful API, it wassuddenly feasible to work

with 1,000 partners: Heres my

endpoint; integrate with it.

Steven Willmott, CEO, 3scale


9/13

informationweek.com

switched from a clumsy, tacked-on mobile

website to a set of APIsthat allow retrieval of

flight schedules, reservations, and cargo and

baggage information. That effort has led to

a number of mobile apps that have proved

much more successful than the mobile web-

site. Rovi, a provider of entertainment meta-

data for companies including Pandora and

Spotify, switched from distributing its data

as flat-file databases to using a RESTful API,

which lets it be more flexible with its licens-

ing contracts while giving it much greater

control the data stays in-house, and APIs

can be altered as needed. Edmunds.com has

grown into one of the worlds best sources

for automotive data, and its API strategyhas

been a big part of its most recent successes,enabling it to stop individually managing

code for each partner and instead focus on

maintaining and improving a standard set of

APIs. Less effort, more scalability. For ideas,

check out the @EdmundsAPITwitter account,

which highlights new use cases, implementa-

tions and improvements in its API program in

a developer-friendly context.

Sold on the benefits of APIs? Great. But lets

be clear: IT organizations cant move unilat-

erally. APIs exist to serve business needs, so

dont write line one of code until you have a

clear business case. And that begins with de-

ciding how core APIs will be to your company.

Some experts, including Daniel Jacobson,

the creator of the NPR A

director of engineering f

see APIs as a tactic, not a


1. Usage tiers are a smart idea. Your API need not be either free or premium. Maps API; its one of the most-used embedded APIs. Google provides free access for

youre using it for something like a for-profit fleet management or asset tracking app

Apps for Business license. This lets small developers get their apps off the ground and

Google retains that business later.

2. Dont skimp on samples.Getting developers to use your API is critical, and sfull SDKs, will help attract them. Microsoft offers a rich set of API samples in its.NET L

ing collaboration features to apps.

3. Think about the end customer. As we discuss in our column on apps versudoesnt let people do something really useful, you may as well not bother. An examp

for prescription refills using the camera on a smartphone.

4. Content is a product. The Guardian offers open APIs that enable third partietent, up to 1 million articles, in tiers from free to partnerships with content in exchan

enue. If you make great content, consider sharing it via an API.

5. APIs and mobility are better together. As 3scale explains,an API-centric bile strategy creates a stable abstraction layer between internal resources and a chan

applications, device types and partners. Twitter and Starbucks are top examples.

6. Never assume your API cant be found. Even closed, or dark, APIs may sometimes with security implications. A closed API may make the most sense for you

careful not to inadvertently leave a back door open. This happened to Hulu last year,

documented REST API that returned internal data came to light.

6API Best Practices


10/13

informationweek.com

including 3scales Willmott, counter that the

business benefits of APIs are so significant

that they may end up driving the companys

direction.

Our take is that any organization that de-

velops software for internal or external

use should be working on an API strategy.

As with shadow IT, where your employees

will sign up for Dropbox if you dont provide

a similar, sanctioned service, your developers

will define your API strategy if you dont. You

cant afford to sleep while your competitors

build smooth on-ramps into their systems for

your current and potential partners.

The steps to a successful API break down

into three sections: Define the business need,

implement the API technically and maintain

the API. CAs Sirota identifies three business

benefits of implementing an API: reaching

new customers, creating new revenue and

making processes more efficient. If you cant

realize any of those benefits from an API proj-

ect, dont bother.

Not sure where to find the business ben-

efits? 3scales Willmott sees five common API

use cases:

>> Become a platform.

100, or more partners that

added services on top of y

ucts, build an API to becom

>> Enable distribution

ners that could rebundle, r

your products (physical, d

build an API to reduce fric

like those catalogue merc

divulge product lists let

plete transactions and sha

>> Build for mobile. Yo

one or more mobile apps

put a proper API in place,

tional platforms or eve

improving what you have

mare. Mobile commerce isdriver. In our Information

merce Survey, 51% of tele

in their companies mobile

gies say their companies

programs.

>> Enhance your repor

ration. Enterprises have

ises client-server softwa

cations and SaaS and

reporting. Gathering com

from all your critical syst

is vital for getting useful


Does your network or systems team have personnel who can write and maintain scripts that enable integration withthe APIs used to automate deployments?

38%

19%

9%

21%13%

Scripting Expertise

Data: InformationWeekDevOps Survey of 318 business technology and application development professionals, October 2013

Yes, and theyre experts

Dont know

No, and no plans

No, but were working on it

Yes, but were just developing this skill set

8

19

9%

2113


11/13

informationweek.com

combos can be built through APIs much

more efficiently than alternative methods.

In particular, can we all finally dump slow,

clunky protocols, such as EDI and AS2, that

are just shuttling data around via FTP and

dont help at all when it comes to combining

information and worse, are implemented

differently by different entities? I nstead,

with a good API strategy, a company can

expose valuable data in particularly useful

ways, standardize reporting, boost collabo-

ration, and make business insights easier to

uncover.

>> Empower your marketing team. An

agile marketing team with API access to key

operational data can create cool materials,

presentations, and even Web-based ROI cal-culators on the fly.

Once youve found your business case, build

the API. Apigees Ramji warns his customers

not to get hung up on technology choices:

Democracies hate governance but love cura-

tion. Instead of dictating technology, focus

on the core concerns youd have with any

software development project that has a de-

cent number of users: design, security, and

documentation.

From a design standpoint, recall the words

of Bechtels Reilly on multispeed develop-

ment environments. Some APIs wont needrobust architectures or strict service-level

agreements for example, a marketing team

setting up an API strictly for internal use. For

other APIs, designs must scale, be flexible for

future enhancements, and be capable of in-

tegrating with various systems SAP, main-

frames, Oracle, Salesforce.com.

A common factor limiting performance is

the speed of on-premises systems, Masherys

Zazueta says, so design and set expectations

accordingly.

The most common choice for API security

is the OAuth authorizatiolets users authorize on

transactions with anothe

behalf; an example is aut

post tweets for you, with

your Twitter password. B

tion, think about how yo

age: rate-limiting (per sec

kilobyte); restricting acce

points based on user typ

ety of user roles.

Last but not least, cre

that makes it as easy as p


I

f all this API management sounds like

a lot of work, dont fear. Theres a fast-

growing industry helping organizations

manage most of the tricky, annoying ele-

ments of running APIs. Companies includ-

ing 3scale, Apigee, Layer 7, and Mashery

sell platforms and services that handle the

complicated yet mundane elements of sup-

porting APIs, like providing a unified au-

thentication infrastructure and front end to

a variety of internal APIs.

These vendors have exp

the particulars of access c

with various systems and

resources to developers.

vices a slightly different c

enterprises with most of t

on-premises to cloud-base

pays to engage the right e

developers focus on busi

ects as opposed to reinv

J

API Management FirmsVENDOR LANDSCAPE


12/13

informationweek.com

ers to work with your API. In the best cases,

these instructional assets go beyond dry-as-

toast manuals; think videos and Web sand-

boxes like what Google offers.Zazueta rec-

ommends that you think about the developer

experience with your API just as much as you

think about the user experience with yourwebsite and mobile apps.

Youre not done once youve implemented

your API; youve just started, in fact. In ad-

dition to supporting in-house developers,

consider the ultimate end users of your API,

such as dev teams at partners and suppliers

or even mobile app developers. Just as you

might reach out to focus groups of longtime

customers of your companys products, cozy

up to the biggest users of your API, regardlessof whether they discovered it published on

the Web or have been a partner for years. See

what they like and dont like about it.

Your APIs are products, and you need to

treat them as such.

Where Do We Go From Here?

Remember the uproar when an internal

rant former Amazon employee Steve Yegge

wroteto his co-workers at Google went pub-

lic? Yegge was referencing a long-standing

mandate by Amazon CEO Jeff Bezos to Ama-

zon employees requiring that each team

expose its data and functionality through

interfaces, and that all interteam communi-

cations be conducted through those inter-

faces: There will be no other form of inter-

process communication allowed: no direct

linking, no direct reads of another teams

data store, no shared-memory model, noback-doors whatsoever. The only communi-

cation allowed is via service interface calls

over the network.

Oh, and all interfaces were required to

be designed from the ground up to be ex-

ternalizable. As one commentator to the

rant exclaimed, Think about what Bezos

was asking! Every team within Amazon had

to interact using Web services. If you were

human resources and you needed some

numbers from marketing, you had to get

them using an API.

Not every company is li

this a vision that will grad

ery enterprise, or are ther

etration of APIs? CAs Sir

of enterprise-as-a-servi

that the future looks like

ness processes connectedSirota, the enterprise beco

first having departments

then the CIO sees signifi

cies in shared services, a

separate, successful APIs b

API platform.

Consider how Amazon

Web bookstore to a produ

and from selling shipped

ternet to actually selling structure on demand t

a service -oriented archit

think you have to rewrite

there; Sirota sees a lot of

on, which he describes as

thinkits a known prob

solution.

In short dont bet agai

APIs that accelerate its inte

Joe Mast ers Emiso n is CTO of B

[email protected].


Mobile apps are much chattierthan desktop Web applications,

sending 20 to 30 small messages.

They require a different strategy.

Sam Ramji, VP of strategy at Apigee


13/13

informationweek.com

READER SERVInformationWeek

breaking IT news, a

Electronic Newsle

InformationWeek D

informationweek.c

Events Get the lat

events at informat

Reports reports.in

for original researc

How to Contact U

informationweek.c

Editorial Calenda

Back Issues

E-mail: customerse

Phone: 888-664-33

847-763-9588 (Out

Reprints Wrights

Web: wrightsmedi

E-mail: ubmreprint

List Rentals Spec

E-mail: PeterCan@

Phone: (631) 787-3

Media Kits and Ad

createyournextcus

Letters to the Edit

[email protected]

company, city, and

Subscriptions

E-mail: customerse

Phone: 888-664-33

847-763-9588 (Out

Copyright 2013UBMLLC.All r

SALES CONTACTSWESTWestern U.S. (Pacific and Mountain states)

VP & National Co-Chair, Business Technology

Media Sales, Sandra Kupiec

(415) 947-6922, [email protected]

District Sales Manager, Vanessa Tormey


Account Director, Ashley Cohen


Account Director, Vesna Beso(415) 947-6104, [email protected]

Account Director, Matthew Cohen-Meyer


SALES CONTACTSEASTMidwest, South, Northeast U.S. and Canada

VP & National Co-Chair, Business Technology

Media Sales, Mary Hyland


Eastern Regional Sales Director, Michael Greenhut


District Manager, Jenny Hanna


District Manager, Cori Gordon


STRATEGIC ACCOUNTSAccount Director, Jennifer Gambino


Strategic Account Director, Amanda Oliveri


SALES CONTACTSMARKETINGAS A SERVICEDirector of Client Marketing Strategy,

Jonathan Vlock


SALES CONTACTSEVENTSSenior Director, InformationWeek Events,

Robyn Duda


MARKETINGVP, Marketing, Winnie Ng-Schuchman


Director of Marketing, Monique Lutrell


Marketing Assistant, Hilary Jansen


UBM TECH

Paul MillerCEO

Marco PardiPresident, Events

Scott MozarskyPresident, Media and

Partner Solutions

Kelley DamoreChief Community Officer

David MichaelCIO

Simon CarlessExec. VP, Game & App Development

and Black HatLenny HeymannExec. VP, New Markets

Angela ScalpelloSr. VP, People & Culture

Business Contacts

Print, Online, Newsletters, Events, Research

Lorna Garey Content Director, Reports

[email protected] 978-694-1681

Mary Ellen Forte Senior Art [email protected]

Jim Donahue Managing Editor

[email protected]

Shane ONeill Managing Editor


Rob Preston VP and Editor In Chief


Chris MurphyEditor


Previous Next

Documents

InformationWeek "Age of API" November 2013