DZone
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
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
What's in store for DevOps in 2023? Hear from the experts in our "DZone 2023 Preview: DevOps Edition" on Fri, Jan 27!
Save your seat
  1. DZone
  2. Data Engineering
  3. Databases
  4. API Lifecycle Service Providers Instead of Walled Gardens

API Lifecycle Service Providers Instead of Walled Gardens

I want my API service providers to be modular, flexible, and agile, and provide a mix of valuable API resources that I can use across my own API lifecycle.

Kin Lane user avatar by
Kin Lane
·
Feb. 24, 17 · Opinion
Like (3)
Save
Tweet
Share
4.99K Views

Join the DZone community and get the full member experience.

Join For Free

It is a common tactic of older software companies to offer open-source services and tools in a way that all roads just lead into their walled garden. There are many ways to push vendor lock-in, and the big software vendors from 2000 through 2010 have mastered how to route you back to their walled gardens and make sure you stay there. Web APIs have set into motion a shift in how we architect our web, mobile, and device applications, as well as providing services to the lifecycle that are behind the operation of these web APIs. While this change has the potential to positive, it often can be very difficult to tell apart the newer breed of software companies from the legacy version amidst all the hype around technology and startups.

I've been having conversations recently which are pushing me to think more about middleware, or what I'd refer to as API lifecycle tooling. In my opinion, these are companies who are selling services and tools to the API lifecycle, which in turn is fueling our web, mobile, device, and other applications. In my opinion, as a server provider, you should be selling to a company and API provider's lifecycle needs, not your walled garden needs. I understand that you want all of a company's business and you want to lock them into your platform, but that was how we did business 10 years ago.

The API service providers I'm shining a light on in 2017 are servicing one or many stops along the API lifecycle, supporting API definitions and providing value without getting in the way or locking customers in. They do this on-premise or in the cloud of your choice and allow you to seamlessly overlap many different API service providers providing a variety of solutions across the API lifecycle. You will notice this patterns in the companies I partner with like APIMATIC, Restlet, Tyk, and Dreamfactory. I find I have a lot more patience when it comes to the whole startup thing if your service is plug and play and us API providers can choose where and when we want to put your tools and services to use.

I want my API service providers to behave just like they recommend to their customers: modular, flexible, agile, and providing a mix of valuable API resources I can use across my own API lifecycle. You'll find me doing more highlighting of what I consider to be API lifecycle service providers who bring value to the API life cycle with API definitions like the OpenAPI Spec as the center of their operations.

API Web Service

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

  • The Enterprise, the Database, the Problem, and the Solution
  • Promises, Thenables, and Lazy-Evaluation: What, Why, How
  • AIOps Being Powered by Robotic Data Automation
  • How to Cut the Release Inspection Time From 4 Days to 4 Hours

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • 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: