It's worth pointing out that they count the datacenter and support costs for their free accounts under Sales and Marketing.
That's great as long as you're using something with efficient random-access (SQL). If your datastore/back-end is btree-based, however (say, CouchDB for example, or Google search results) you're better off with 'next',…
We're working with a HATEOAS API on our current project. One area it really shines is in pagination. The API abstracts away both a MySQL and a CouchDB database. When paginating through SQL, the "next" and "prev" links…
The Esteban one? "I don't always write Linux Kernels" "But when I do, it's in browser hosted Javascript"
It's worth pointing out that they count the datacenter and support costs for their free accounts under Sales and Marketing.
That's great as long as you're using something with efficient random-access (SQL). If your datastore/back-end is btree-based, however (say, CouchDB for example, or Google search results) you're better off with 'next',…
We're working with a HATEOAS API on our current project. One area it really shines is in pagination. The API abstracts away both a MySQL and a CouchDB database. When paginating through SQL, the "next" and "prev" links…
The Esteban one? "I don't always write Linux Kernels" "But when I do, it's in browser hosted Javascript"