Open Source And Open APIs, Facebook-Style - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Government // Enterprise Architecture
Commentary
5/29/2008
08:08 AM
Serdar Yegulalp
Serdar Yegulalp
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Open Source And Open APIs, Facebook-Style

The more I read Facebook's statement about opening its platform to third-party developers, the more it seems like you could interpret what they say as a promise to open just their APIs, or both their APIs and their underlying platform code.  Which one's more likely?  Better to ask: which one makes the most sense for Facebook, or any other Web compan

The more I read Facebook's statement about opening its platform to third-party developers, the more it seems like you could interpret what they say as a promise to open just their APIs, or both their APIs and their underlying platform code.  Which one's more likely?  Better to ask: which one makes the most sense for Facebook, or any other Web company?

I'm betting in this case that it's only a set of APIs, or at most APIs plus the code for a toolset that isn't the core of Facebook itself.  But that's not a moral pronunciamento; it's just a reflection of what Facebook is.  Companies like Facebook -- or Google, or Amazon -- make their living by selling a product or reselling some part of their service in a controlled way.  Providing APIs for their services makes more business sense to them than providing their platform code.

There's no reason Facebook can't do both, though; it's largely a question of scope and what they want to accomplish with it.  One thing I'm sure they don't want to accomplish, though, is to make it possible to no longer have to rely directly on Facebook to get what they offer.  As long as their business model involves being unique as a service, they'll do what it takes to remain unique.

Contrast this with a company providing a wholly open platform, code and APIs alike (easy example: MySQL).  They're going to profit by dint of offering something else that's unique.  Typically, it's managed support or other direct-sales expertise -- in other words, they're still reselling the brains behind the outfit, just in a different package.

So which one's better, and not just in the sense of which is better for my immediate needs?  For many people, an open API to a relatively insular platform is going to be "open enough" for them.  But if you'd rather not depend wholly on any one outfit to supply a set of APIs, then an API set alone won't do.  I'm curious to see which way the majority of Facebook users opt to go.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

Slideshows
10 Things Your Artificial Intelligence Initiative Needs to Succeed
Lisa Morgan, Freelance Writer,  4/20/2021
News
Tech Spending Climbs as Digital Business Initiatives Grow
Jessica Davis, Senior Editor, Enterprise Apps,  4/22/2021
Commentary
Optimizing the CIO and CFO Relationship
Mary E. Shacklett, Technology commentator and President of Transworld Data,  4/13/2021
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Planning Your Digital Transformation Roadmap
Download this report to learn about the latest technologies and best practices or ensuring a successful transition from outdated business transformation tactics.
Slideshows
Flash Poll