Skip to content

Hw 3 #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ByBinPy wants to merge 11 commits into
base: hw-2
Choose a base branch
from
Open

Hw 3 #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
9c76cb1
HW-3 is Start.
21092004Goda Oct 2, 2025
58e3c14
refactoring: refactored di in spring
Oct 2, 2025
68b9ff6
refactoring: fixed wildcard imports and reformate code
Oct 2, 2025
28b304a
Merge pull request #9 from ByBinPy/feature/hw-3-ivm
ByBinPy Oct 2, 2025
74a87c3
hotfix: fixed bean resolution in constructor
Oct 2, 2025
86e0d3c
feature: added counters
Oct 3, 2025
3970682
feature: added counters
Oct 3, 2025
21e6f81
feat: new dashboards for active tasks
Oct 10, 2025
6aabbfd
fix: unused imports
Oct 10, 2025
2a456a1
fix: fixed dashboard description and added metric for queue monitoring
Oct 16, 2025
8ea5050
Merge pull request #11 from ByBinPy/feature/hw-3-active-tasks-dashboards
ByBinPy Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified .gitignore
View file
Open in desktop
Binary file not shown.
15 changes: 12 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
# Template for the HighLoad course

This project is based on [Tiny Event Sourcing library](https://github.com/andrsuh/tiny-event-sourcing)

### Run PostgreSql

This example uses Postgres as an implementation of the Event store. You can see it in `pom.xml`:

```
Expand All @@ -12,7 +14,8 @@ This example uses Postgres as an implementation of the Event store. You can see
</dependency>
```

Thus, you have to run Postgres in order to test this example. Postgres service is included in `docker-compose` file that we have in the root of the project.
Thus, you have to run Postgres in order to test this example. Postgres service is included in `docker-compose` file
that we have in the root of the project.

# More comprehensive information about the course, project, how to run tests is here:

Expand All @@ -21,19 +24,25 @@ https://andrsuh.notion.site/2595d535059281d8a815c2cb3875c376?source=copy_link
https://andrsuh.notion.site/2625d5350592801aaf88c7c95302d10c?source=copy_link

### Run the infrastructure

Set of the services you need to start developing and testing process is following:
- Bombardier - service that is in charge of emulation the store's clients activity (creates the incoming load). Also serves as a third-party payment system.

- Bombardier - service that is in charge of emulation the store's clients activity (creates the incoming load). Also
serves as a third-party payment system.
- Postgres DBMS
- Prometheus + Grafana - metrics collection and visualization services

You can run all beforementioned services by the following command:

```
docker compose -f docker-compose.yml up
```

### Run the application
To make the application run you can start the main class `OnlineShopApplication`. It is not being launched as a docker contained to simplify and speed up the devevopment process as it is easier for you to refactor the application and re-run it immediately in the IDE.

To make the application run you can start the main class `OnlineShopApplication`. It is not being launched as a docker
contained to simplify and speed up the devevopment process as it is easier for you to refactor the application and
re-run it immediately in the IDE.

### If you want to pull changes from the main repository into your fork

Expand Down
Loading