A self-build API, in my opinion, allows for more flexibility and
integration with third-party services (such as the Ubuntu Reviews API)
than a generated API from Couchbase. It may not necessarily be easier
to maintain, however we'll be able to add / remove features at our own
speed and not rely on potential breaking changes by Couchbase.
One could say that we could just stick with a particular version of
Couchbase to ensure things don't break, but that opens up the doors for
future security exploits and vulnerabilities.
On Mon, Mar 25, 2013 at 5:20 PM, Goncalo Margalho <g...@margalho.info>
wrote:
Why should we "waste" time on building an API for it if we could just
build the database with couchbase (which is very scalable as well)
and just use those ones, they are there, we just need to prepare the
queries (if needed) I could help setting up everything.
http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-views-querying-rest-api.html here
you can see an example, the APIs are generated automatically. I can
set up the infrastracture, define the DB with someone and just make
some tests :)
On Tue, Mar 26, 2013 at 12:18 AM, Joshua Strobl
<truthfroml...@gmail.com> wrote:
I do want to say, Goncalo, since I forgot to mention it in my prior
email, that if you could work on setting up and maintaining the
infrastructure, I can handle the API.
You'd have my love...or a cookie. Whatever you prefer. A cookie
sounds better.
- Joshua Strobl
--
Mailing list: https://launchpad.net/~elementary-dev-community
Post to : elementary-dev-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~elementary-dev-community
More help : https://help.launchpad.net/ListHelp
