For the Couchbase Connect Silicon Valley conference last fall we built one of the most extensive demonstrations of the Couchbase Data Platform capabilities ever using a combined web and mobile application. The application incorporates dynamic N1QL queries, offline mobile, IoT sensors, ad hoc queries with analytics, cross-data center replication, failover, fuzzy text matching, and a slew of other features. In short, we aimed to show the core of a complete, realistic use, based on a real data standard (FHIR) used in healthcare. Check out the video from the conference here.
A deployment of this complexity necessarily requires quite a bit of setup. Along with the source code for the project, I’ve included both regular shell scripts and scripts to use with Docker to simplify running the demo yourself.
Sometimes seeing it all put together by hand is really helpful, though. With that in mind, I made a video showing every step needed to configure the demo. I go quickly, and sped up parts to get it all crunched in to 15 minutes. (Realistically, even with practice, it takes about 1/2 an hour.)
Watch the full video, or use this table of contents to jump to sections directly.
Table of Contents:
00:33 – Web Server and Client Setup
01:15 – Server-Side Urban Airship Configuration
01:51 – Couchbase Server Basic Setup
03:04 – Bucket Creation
03:34 – RBAC
04:00 – Query Index Creation
04:42 – Eventing Service
05:54 – cURL Access Restrictions
06:20 – Configuring Analytics
07:02 – Full-Text Search
10:22 – Importing Data
11:52 – Start Sync Gateway
12:29 – Mobile Application
Feel free to post questions in the comments section of the video, on our forum, or you can reach me directly on Twitter.
Couchbase is open source and free to try out.
Get started with sample code, example queries, tutorials, and more.
Find more resources on our developer portal.
Follow us on Twitter @CouchbaseDev.
You can post questions on our forums.
We actively participate on Stack Overflow.
Hit me up on Twitter with any questions, comments, topics you’d like to see, etc. @HodGreeley