Skip to content

Commit 3e8e291

Browse files
authored
docs: updates architecture diagram and added details in README (#22)
* docs: updated readme with arch and other details * fix: addressed gurtej's comment
1 parent 09c8b45 commit 3e8e291

File tree

1 file changed

+48
-1
lines changed

1 file changed

+48
-1
lines changed

README.md

Lines changed: 48 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,51 @@
11
## Config Service
22
Service for storing and serving configurations across multiple services and contexts.
33

4-
Refer [config_service.proto](config-service-api/src/main/proto/org/hypertrace/config/service/v1/config_service.proto) for Config Service APIs
4+
## Description
5+
6+
[config service](https://github.com/hypertrace/config-service) is a place to store configuration data such as user preferences, saved query filters, ingestion config, etc. Many of these use cases have not yet been built out. In general, this service is meant for user-managed configuration that needs to be persisted, and contains support for version history, auditing etc. In the past, we've addressed such things by spinning up individual services (such as attribute service). As new features get built out, we want to avoid that (and eventually to merge older services back into this).
7+
8+
| ![space-1.jpg](https://hypertrace-docs.s3.amazonaws.com/arch/ht-arch.png) |
9+
|:--:|
10+
| *Hypertrace Architecture* |
11+
12+
Refer [config_service.proto](config-service-api/src/main/proto/org/hypertrace/config/service/v1/config_service.proto) for Config Service APIs.
13+
14+
## Building locally
15+
The Config service uses gradlew to compile/install/distribute. Gradle wrapper is already part of the source code. To build Config Service, run:
16+
17+
```
18+
./gradlew dockerBuildImages
19+
```
20+
21+
## Testing
22+
23+
### Running unit tests
24+
Run `./gradlew test` to execute unit tests.
25+
26+
### Running integration tests
27+
28+
Run `./gradlew integrationTest` to execute integration tests.
29+
30+
31+
### Testing image
32+
33+
To test your image using the docker-compose setup follow the steps:
34+
35+
- Commit you changes to a branch say `config-service-test`.
36+
- Go to [hypertrace-service](https://github.com/hypertrace/hypertrace-service) and checkout the above branch in the submodule.
37+
```
38+
cd config-service && git checkout config-service-test && cd ..
39+
```
40+
- Change tag for `hypertrace-service` from `:main` to `:test` in [docker-compose file](https://github.com/hypertrace/hypertrace/blob/main/docker/docker-compose.yml) like this.
41+
42+
```yaml
43+
hypertrace-service:
44+
image: hypertrace/hypertrace-service:test
45+
container_name: hypertrace-service
46+
...
47+
```
48+
- and then run `docker-compose up` to test the setup.
49+
50+
## Docker Image Source:
51+
- [DockerHub > Config service](https://hub.docker.com/r/hypertrace/config-service)

0 commit comments

Comments
 (0)