Event persistence

[rosscado]

Save resources to a backend database.

[rosscado]

Accomplishments so far:

• GET /events resources are retrieved from a persistent document store.
• POST /events resources are attributed id attributes (transient).
• Unit tests use a different (test_events) database to production (events).

[rosscado]

Single DB Instance

I only have a single Cloudant database instance available under the Lite/free plan.
I have bound the instance to the staging space app, leaving it unavailable to the production app. For this reason production can't be started for now.

Implement Transient Functionality First

I am pausing completion of the persistence feature until I have more functional work done first, specifically implementing event APIs #2

[rosscado]

Entity Relationships

Our entity/resource documents will sometimes contain nested entities/resources that are best represented as their own documents, rather than embedded.

This article explains how to represent such a relationship in a Cloudant/CouchDB NoSQL database: https://wiki.apache.org/couchdb/EntityRelationship

Example (many:1 relationship)

Model:

---
_id: event_id
type: event
organising_club_id: club_id
---
_id: club_id
type: club

Client logic:

club = {'title': 'Little Club'}
club = db.create_document(club)
event = {'title': 'Big Race', 'organising_club_id': club['_id']}
event = db.create_document(event)

Views (1:many relationship)

No view is required for a 1:1 or many:1 relationship. Views are required for 1:many relationships.