Open API: Architectural Choices and Considerations

By Dominiek ter Heide | Published: May 29, 2008

Recently I’ve been working a lot on thinking out and building up the upcoming Data Services for iknow.co.jp. I’ve composed a quick slideshow of all the architectural choices and considerations I’ve come across.

Building API’s for a web 2.0 / web 3.0 aspiring service is very different than providing a tight integrated RPC service for some corporate client. It requires completely different ways of thinking and embracing new standards.

| View | Upload your own

This entry was posted in Uncategorized. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *

Name *

Email *

Website

Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Additional comments powered by BackType

About this Blog

Hi, I'm Dominiek, co-founder of a stealth startup, former CTO at Smart.fm and owner of Synaptify Consulting. This blog is about Startups, Technology and Hacking. One big re-occurring topic is the convergence of several web technologies that create the so-called Synaptic Web.

Follow me on Twitter Subscribe to RSS!
Previous Articles
In the Past

Open API: Architectural Choices and Considerations

Post a Comment

About this Blog

Previous Articles

In the Past