@@ -62,6 +64,8 @@ alternate between the two dataset containers to balance the load. If
one dataset server is down, temporarily or long run, the cache server
should attempt to use the other dataset server to obtain the result.
**Hint:** think about whether there is any .sh script that will help you quickly test code changes. For example, you may want it to rebuild your Dockerfiles, cleanup an old Compose cluster, and deploy a new cluster.
## Part 1: gRPC Server (Dataset Layer)
Define an RPC service in a .proto file called "PropertyLookup". It
...
...
@@ -158,9 +162,16 @@ Specifications:
Read the directions [here](../projects.md) about how to create the
repo.
At a minimum, your submission repo should contain the following:
`docker.txt`, `compose.txt`, `download.sh`, `multi.sh`, and
`Dockerfile`.
You have some flexibility about how you write your code, but we must be able to run it like this:
```
docker build . -f Dockerfile.cache -t cache
docker build . -f Dockerfile.dataset -t dataset
docker compose up -d
```
We will copy in the "docker-compose.yml" and "addresses.csv.gz" files,
