Why not cache the github data in memory or using in memory db instead of having PostgreSQL dependency

[arturmkrtchyan]

If the project get's data from github why not cache in memory or using in memory db instead of having PostgreSQL dependency ? AFAIK without DB this project will have higher chances of adaptability.

[rwitzel]

BACKGROUND

CatWatch supports two basic use cases:

1. Display the current state of the open source activities of specific GitHub accounts.
2. Display historical data regarding the open source activities (time series).

The second use case requires the persistence of time-series databases. Maybe it makes sense to separate the code of both use cases.

At the moment both use cases require a database. Theoretically, a in-memory database can be used (and is used in some integration tests). By default, i.e. without additional start-up parameters, an in-memory database is used.

In case CatWatch should not take care of historical data but only provide data for the current state, the application should fetch up-to-date data immediately after the start-up. This is the use case that could be implemented by this issue.

TASK

When the application is started with parameter -Dfetch_data_after_startup=true Then the application fetches the current statistics from the database immediately after the start-up

[rwitzel]

As a reminder, there are several projects that display the current state of the open source activities: https://docs.google.com/presentation/d/1Kq_7vSj8Ah4JBvLapSkkAAlcq9jO6NMqjm3y-Pt4UpM/edit#slide=id.gb681a976b_0_34 , made by Adobe, Microsoft etc.