Database and API

• Periodic update announcements here.

Couchdb

API-s

• Querying quote entries: use the database and the index_headwords index
  • Get a particular entry: link.
  • Get 20 some quotes starting with ast: link .

Database replicas

• You want to host a repilica and make things faster for folks in your geographical area? Just open an issue in this project and let us know.
• Ahmedabad, IN http://vedavaapi.org:5984/quote_db__sa/_all_docs
• Bay area, USA (dev machine, unstable) http://vvasuki.hopto.org:5984/quote_db__sa/_all_docs

Technical choices

• Use Nosql rather than a relational database as the primary canonical database.
  • Reasons (from here ):
    • The need to develop with agility
      • Simplicity (less need to join n tables)
      • Flexibility (schema can easily be changed)
    • distributed nature: ability to operate at any scale.
      • Database copies can sync with each other easily - no centralization is good.
  • Comparison here .
  • Alternatives for mobile offline use:
    • Couchbase database, since it can be used in many mobile OS-s.
      • Comparison with mongodb: on cb site.
    • Realm.io - good for storing plain Java objects via JSON.
    • Google Firebase for key-value storage - 1GB free.
• Scala for the ingestion libraries (same justification as expressed here ).

Code Contribution

Links to general comments

See indic-transliteration/README for the following info:

• Setup
• Deployment
  • Regarding maven targets in intellij
  • Releasing to maven.
  • Building a jar.
• Technical choices
  • [Scala](https://github.com/sanskrit-coders/indic-transliteration/blob/master/README.md#scala