Topic: Architecture for an api centric application.
Got the opportunity to put Ruby into a new site/project. Present system is a number of disperate websites, php etc with web forms submitting to a central database via email processors.
I'm loooking to streamline this via a ror island/data centre. The primary interface would be an api to take posted data from the external sources, mash it about and export it again.
Does anybody have any pitfall advice at a high level for this sort of concept?
I'm thinking of taking a restful approach, I seem t get on with it. I'm shying away from a large single transaction, rather a number of trips to capture data as the user completes sections of the form(s). Also site A may have 3 or 4 times the data requirements site B has so thats a factor, core data remains a near costant of name contacts etc...
Also keen to know of anybody who has api key token like ideas, so rather than a plain username password, a key to authenticate against, aka google maps. Building an api does seem straight forward and I'm wary of a path that appears all to easy...no matter how much I love the ruby concept Certainly to post and read xml data is considerably easier than any java I've ever had to build.
My goal is a basecamp esq ease of use for the api from java, php and .net apps, just seem to have too many blank bits of paper, maybe I need to fire up textmate and just start
Look forward to any comments from experts and other keen parties
Last edited by colindensem (2007-01-12 20:58:29)