- mvn clean install
- docker-compose up -d --build
The aim to this project is to implement distributed cache like redis. A distributed cache is split across multiple systems and a way of providing faster access to the contents of the database. Distributed cache should provide good scalability and fault tolerance.
Evaluate each of the architectural style and find out which is the most suitable and feasible style for our project. Some of the things that we are looking for here is support for peer to peer calls and asynchronous calls.
- Pros 1. 2. 3. - Cons 1. 2. 3.
The data below would evaluate our support for sql and no sql databases. Given the amount of time, ho feasible is it to support each of the database
- Pros 1. 2. 3. - Cons 1. 2. 3.
- write through cache
- write back cache
- write around cache
- LRU
- LFU
- MRU
- Package names should include small letters(a - z).
- Classes should start with capital letters and follow PascalCase
- variables and functions should have camelCase letters
[1] https://www.infoworld.com/article/3262990/how-to-implement-a-distributed-cache-in-aspnet-core.html
[2] https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html