/public/api/v1. — Don’t do this!

If you are anything like me, or tens of thousands of others working in the web development domain, you know what the title means. We are going to talk about the widely debated “v” in API endpoints. Do I like it? Well, obviously not. I’ll tell you why. 1. It’s ugly! It makes reading documentations very difficult, because you’ll need to version your document as well. And you’ll have to make sure you are using the latest document, or the document that’s relevant to the version of API you are consuming. Wouldn’t it be a lot easier if you had one version of API and one version of documentation? I know what people over at the other camp are shouting — your APIs will change and you need to have versions. I agree, and I’ll tell you how I prefer to handle those changes later. 2. If y...

Read More

It’s time to move your platform to RESTful APIs

If you are into tech, there’s a good chance you already know what’s a web API. All the cool kids use it these days. It’s the new kid on the block. And it’s sexy with well defined features. Web APIs aren’t necessarily new, they’ve been around for a while. Even RESTful APIs aren’t that young. But that’s not what we are here to talk about. We are here to see why it’s time to move your platform to a more modern architecture which exposes a bunch of (RESTful) APIs for the rest of the world to add value to your platform. As a person who’s been producing and consuming APIs for the last few years, I’ve seen a lot of them. I’ve had projects where I was required to get and send data to third party servers, and this is where RESTful APIs come in. I’ve seen tens of thousands of them, scrolled ...

Read More