Design reader and writer implementation for clients which wants to read and write the database. (Should support different strategies/ some client can just write/ some will just read)/. Follow up to handle race conditions and stuff.
You are expected to design a working code architecture for a problem. Just to explain for this particular problem, what is expected from you is
- What interfaces and methods will you make?
- What design patterns will you apply if applicable?
- How clean and extendable is your code?
Depending on your usecase, you can define how to fetch anything from this table. It can be
always from the master table
write in master, read from slave
redis-mysql strategy - write to master, replicate in slave but fist read from redis, if not found then read from slave.
They were not looking for any database, they were looking towards the abstraction of a database or what we call a DAO layer.
Design a library/set of abstraction layers which can switch database source from behind for difference use cases. Use-case example - myql for my service and json file for test cases. It is designing a program using OOPS using which we can connect different dbs like mysql, cassandra etc on the fly.