New answers tagged

4

Based on your image, something like the following will be fine (using a RDBMS solution): create table articles ( article_id integer PRIMARY KEY, title varchar(256) NOT NULL, url varchar(256) NOT NULL, summary varchar(256) NOT NULL, body varchar(4000) NOT NULL ); create table article_comments ( comment_id ...


0

I took a look at the REST API endpoint list on the Couchbase docs site. I think it might be hypothetically possible. You could use the N1QL REST API to do inserts, selects, updates, and deletes. I can't say for sure whether this is going to help scaling and load or not, but I do think you're going to have to address a number of other challenges: validation,...


1

You are indeed correct! It is very simple to deploy Couchbase instances and cluster them. This is because Couchbase has a single node type which minimizes configuration, like you've mentioned. What you might not know is that Couchbase has a built in caching layer, eliminating the need to install other caching services to sit next to your database. This ...



Top 50 recent answers are included