An Intro to an API
Building a Digital Sandbox to Play In
I joined Placewise as a Senior Application Developer after a stint as ColdFusion and Flex programmer at Cricket Communications because of their unique opportunity. The people here recognized they were sitting at a potentially profitable confluence of data:
- shopping center events
- store deals
- product info
- shopper brand interest displayed via social networks
- articles on purchasing trends
While the traffic and interactions with the browser based product has been positive my role is to help extend the site’s value to the numerous “other” screens. This includes everything from smart phones to tablets (and beyond). I’m working to compartmentalize pieces of essential functionality into handy, dandy web services TO FEED THE SCREENS.
(It is now time to drop acronyms like Benjamins in a rap video.)
While I did have previous enterprise experience developing SOAP based APIs (ColdFusion makes this ridiculously easy) my current Placewise implementation is REST based. The barriers to entry for new consuming applications are just so much lower. But ease of consumption doesn't mean the process is A-OK. To build this I've been doing things like using a tokenization process for access, securing with basic authorization over HTTPS, clarifying between HTTP POST and PUT, returning tidy JSON, and more. The issues that I've been concerned in this first iteration have been:
- security
- rate throttling
- detecting accidental double postings
- rudimentary caching of essential assets
- bandwidth efficient, mobile network friendly conversations
How do we accomplish these things? Queue the serialized content! More on that in subsequent posts.
Hi there. My name is Matthew Reinbold and I am Vox Pop Design. This is a site where I go on about this, that, and the dreaded other.