couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Bisbee <>
Subject Re: Do we need 2 entry points for the replication?
Date Sun, 22 Jan 2012 18:56:05 GMT
On Thu, Jan 19, 2012 at 11:46 PM, Jason Smith <> wrote:
> On Fri, Jan 20, 2012 at 9:04 AM, Randall Leeds <> wrote:
>>> Exposing features as manipulations to normal documents makes CouchDB's
>>> API simpler and more orthogonal.
>> On the other hand, exposing features via special-purpose APIs hides
>> the implementation and frees us to change how it works under the hood.
> Thank you for not saying "under the covers." Activity under the
> hood--or bonnet--hardly resembles activity under the covers.
> All agree that state is stored in a database. So the question is, have
> a database and an API defined as changes to it (perhaps via _show,
> _list, and _update); or, have a database and an API defined otherwise.
> Either way, you have to bite the bullet and make a breaking change; so
> is hiding the implementation a different matter?

+1 for hiding the implementation. Who says that those other API
endpoints that you would use to manage the replication db will be
around in a year?

We protect ourselves from the future by hiding the implementation
details, thereby not making the same mistake twice.


Sam Bisbee

View raw message