Helping ruby developers to use the best tools for each job so they can solve hard problems, with less bugs and have more free time.
This is a very opinionated post, with some performance tips from someone that uses sidekiq for more than two years now, as as such I have already did some mistakes and learnt some tricks. My current opinion is that sidekiq is the best backend job engine for ruby/rails applications. And of course to use it…
If you are writing an API only rails app, your clients will need to authenticate in some way to use your API, you have of course many options to choose from: You can build your own authentication You can Use a plugin like Devise You can use OAuth both accepting other provider or implementing your…
Following up the post about a Rails API only app, lets talk about why you should not use REST in your API app. 1: too much unneeded information Have you ever written a client application to any API? And when you did it, was there a query you needed to do that returned a lot…
Sometimes we need to create only an API, an application without a user interface, for example if you’ll have someone else built later a mobile client for that API, or even a full SPA web client, there are many reasons to build an API only app. And since there are that many reasons, rails helps…