I Solemnly Swear That I am up to No Good
Who DOESN’T like Harry Potter.
Harry Potter is the book series that got me into reading as a kid – I would spend hours, face pressed up against the pages, oblivious to the events going on around me. I was completely immersed in that world.
So when @phalt_ released a RESTful API providing all the Star Wars data you’ve ever wanted (swapi.co) I thought, “Hmm. Maybe I’ll make an API about something I love!”. Thus, the Idea for the Potter API was born. But what data would I provide to people through this API? And what technology stack would I build it in?
Lets begin with the data I plan on making available through the API:
How many pages? When was it published? Who by? All this information will be included about books, as well as a ‘followed by’ and ‘proceeded by’ field.
Director? Check. Producer? Check. Budget? Check. Ah, but what about revenue? Check. Check. Check.
Names, Date of Birth, Gender, Height, Eye Colour, Wand, Patronus, Animagus, Hogwarts House, Species! I’m hoping to include all of this important information. How else will you know that Lily’s wand was made of Willow and her Patronus was a Doe.
The crux of every Witch or Wizards arsenal.
“You’re gunna go to Hogwarts. You get an Owl. You’ll do Spells and…” – You get the idea.
Now you too can practice the incantation of spells and learn their effects.
The Technology Stack
What should I build all of this in? Well, I want to learn something new; something I haven’t really used before, so I’ve decided to build this RESTful API using Node.js, Express, and MongoDB. The techies amongst you will have noticed that these technologies, along with Angular.js, constitute a MEAN stack.
Well, thats it for now. Hopefully I’ll update you in the near future with the progress of the API and an estimated ‘Go Live’ date for it. In the meantime, visit potterapi.co.uk to keep up to date with when you can get started!