DZone
Integration Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Integration Zone > ''We Want to Do APIs'' - You Already Are, Just Not in an Organized Way

''We Want to Do APIs'' - You Already Are, Just Not in an Organized Way

You need to identify the ways you're already exporting, importing, migrating, syncing, and putting data to work across operations and establish a coherent approach.

Kin Lane user avatar by
Kin Lane
·
Oct. 24, 16 · Integration Zone · Opinion
Like (2)
Save
Tweet
2.47K Views

Join the DZone community and get the full member experience.

Join For Free

I have a number of folks at companies, organizations, institutions, and government agencies come to me saying that they want to do APIs and they need some help. In many of these discussions, the first task centers around addressing the motivations behind this declaration and helping folks realize they are already doing APIs; they're just not doing it in any sort of coherent and organized fashion.

Any business, organization, institution, or government agency is moving machine-readable data between internal and external systems in 2016 for use in a variety of applications. This is done in a variety of often proprietary, ad-hoc, data dump, etc. approaches that are often dictated without any coherent vision. API does not always mean 100% REST. It is about establishing interfaces between systems for programmatic usage across a variety of applications. The trick is to do all of this in a simplified, standardized, consistent, and low-cost way modeled on what has been working for the web. 

You are already doing API. You need to identify all the different ways you are already exporting, importing, migrating, syncing, and putting data to work across operations and begin to establish a coherent roadmap and approach to communicating about all of this. Then, get to work identifying where the opportunities for standardizing how everything is defined, how access is needed, and a baseline for communication around these critical integrations on an ongoing basis. It's not about whether you should do APIs or not. You are already there. It's about how to start doing it in a more organized and coherent way.

Machine-readable data application Data (computing) IT API Baseline (budgeting) Sort (Unix) Interface (computing) Web Protocols

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Vaadin Apps as Native Executables Using Quarkus Native
  • How Java Apps Litter Beyond the Heap
  • Event-Driven Microservices?
  • Container Orchestration Tools Comparison

Comments

Integration Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo