A blog mostly about technology. Infrequently updated.
Every developer sets out to make their REST API perfect when they
start writing it, but, at least from this author's experience, it
often veers as requirements pour in. The following is a small
checklist of things that might indicate you're veering too far.
The secular trend towards APIs is seemingly unbounded. Out of the
excitement will come established companies wanting to get their
slice of the pie and experimenting with presenting their data
through a programmable interface. How do you go about designing one
considering current architecture?
Below are some tips which might just stop you making that one
horrible mistake that makes your CTO wonder if your probationary
period is over.
The following is the tale describing the creation of a flexible
strategy for storing time series statistical data in Redis.
It's a common problem when designing an API but there's no
definitive way to return multiple resources within a single request
that fits in with peoples perception of an idealistic REST
implementation. Here I discuss some options.