Choosing right database for storing bank transactions
Database Administrators Asked by Vojtěch on September 18, 2020
I am starting a new project within GCP and I am trying to choose a right tool for storing bank transactions:
- I don’t need transactions, these will be basically write-only, no updates
- I don’t need joins and relations
- I need grouping and sums
- Ideally I would like to use a managed tool within GCP
- I need to be able to have unique records (identified by ID or by the uniqueness of the record)
GCP solutions:
- Firestore
- I really like the way of authorisation via service accounts, no need for users/passwords
- Fulfils 1, 2, 4, 5
- Completely unsuitable to fulfil point 3
- CloudSQL
- fulfils 3 and 5, but I find it too complex for my need
- old-way authorisation of MySQL – one cannot use GCP authorisation
- Elasticsearch
- fulfils 3 and 5 but also too complex
- Not within GCP, not managed, cannot use GCP auth
- BigQuery
- Seems to fulfil all 1, 2, 3, 4
- Unfortunately it seems it cannot prevent having duplicate records
- Data becomes available after long time
- BigTable
- Seems too complex for such simple requirements
Could you think of another approach?
Add your own answers!