Posted on 04-15-2014
There is a great post over on the Orchestrate.io blog about how they deployed a backend for the MarvelousDB app, using data from the Marvel API, allowing you to explore the world of Marvel comic book characters, through a simple web interface
As developers often face with valuable API resources, the Marvel API leaves a lot to be desired when it comes to available interfaces, data access, and rate limit restrictions. This is common with new APIs, where it takes time to understand the right levers and dials to turn, that will make the API more usable by developers.
Even with these challenges, the Orchestrate team wanted to build the MarvelousDB so they could easily browse the world of Marvel comic book characters, putting the Marvel API to use, but also showing what is possible when using Orchestrate.io. The result is a great example of dynamically building a backend from API resources, in a way that delivers the access and performance you need.
To deliver the MarvelousDB the project employs Node.js, Express.js, Orchestrate.js, Handlebars for templating, and Q for async operations. Using the Marvel API, they pull the data they needed to drive the app, pulling it into Orchestrate.io, giving them the data model and performance they needed, but also adding in capabilities like full text search on top of the data—something that isn’t available from the Marvel API alone.
MarvelousDB is an great example of what is possible via the API driven, database as a service platform Orchestrate.io, but is also a great model to follow when developing web or mobile applications that depend on APIs. Sometimes APIs aren’t structured exactly as we need, and we can use platforms like Orchestrate.io, to well…orchestrate exactly the backend experience we need to get the job done.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API
- Reducing The API Stack Down From 830 to 690
- Gathering My Thoughts Around Common Patterns For Base URLs Across Nearly 700 APIs