Feat/couchdb to postgres migration performace

[rainer-exxcellent]

No description provided.

[github-actions]

Test Results

351 tests  +12   351 ✅ +12   38s ⏱️ -9s
 27 suites + 1     0 💤 ± 0 
 27 files   + 1     0 ❌ ± 0 

Results for commit 995648d. ± Comparison against base commit 30130cb.

This pull request removes 6 and adds 18 tests. Note that renamed tests count towards both.

de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromCouchDbTest
de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromCouchDbTest_noType
de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromCouchDbTest_wrongType
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromCouchDbTest
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromCouchDbTest_NoType
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromCouchDbTest_WrongType

de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromStreamTest
de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromStreamTest_noType
de.bsi.secvisogram.csaf_cms_backend.json.AdvisoryWrapperTest ‑ createFromStreamTest_wrongType
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromStreamTest
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromStreamTest_NoType
de.bsi.secvisogram.csaf_cms_backend.json.CommentWrapperTest ‑ createFromStreamTest_WrongType
de.bsi.secvisogram.csaf_cms_backend.service.AdvisoryServiceTest ‑ changeAdvisoryWorkflowStateTest_badRevision
de.bsi.secvisogram.csaf_cms_backend.service.AdvisoryServiceTest ‑ createNewCsafDocumentVersionTest_badRevision
de.bsi.secvisogram.csaf_cms_backend.service.AdvisoryServiceTest ‑ deleteAdvisoryTest_notFound
de.bsi.secvisogram.csaf_cms_backend.service.AdvisoryServiceTest ‑ deleteAnswer_notFound
…

[github-actions]

Overall Project	81.76% -8.6%	🍏
Files changed	66.79%	🍏

File	Coverage
CsafExceptionKey.java	100%	🍏
AdvisoryListProjection.java	100%	🍏
AdvisoryWrapper.java	93.33%	🍏
AdvisoryEntity.java	89% -11%	🍏
AdvisoryWorkflowUtil.java	88.51%	🍏
CommentWrapper.java	88.4%	🍏
CommentEntity.java	87.88% -12.12%	🍏
AdvisorySearchUtil.java	87.5%	🍏
AdvisoryService.java	77.36% -17.37%	🍏
PostgresRepositoryService.java	73.55% -26.45%	🍏
CounterEntity.java	71.43% -28.57%	🍏
AuditTrailWorkflowEntity.java	71.21% -28.79%	🍏
EntityConverter.java	70.91% -29.09%	🍏
AuditTrailDocumentEntity.java	67.8% -32.2%	🍏
AdvisoryVersionEntity.java	52.54% -47.46%	❌
AuditTrailCommentEntity.java	51.11% -48.89%	❌
AdvisoryListQueryService.java	40.59% -59.41%	❌
DbField.java	0%	❌

[archakisn]

Hi, thanks for this. ENISA is planning a deployment of csaf-cms-backend and the choice of datastore has a direct effect on what we need to provision, since PostgreSQL is already available to us as a managed service while CouchDB would be new.

Is there a rough timeline for this landing, and is it targeted at a particular release? If it is close we would rather wait than deploy on CouchDB and migrate afterwards.

[rainer-exxcellent]

Hi, thanks for this. ENISA is planning a deployment of csaf-cms-backend and the choice of datastore has a direct effect on what we need to provision, since PostgreSQL is already available to us as a managed service while CouchDB would be new.

Is there a rough timeline for this landing, and is it targeted at a particular release? If it is close we would rather wait than deploy on CouchDB and migrate afterwards.

Hello,

the functional implementation is finished.
At the moment we are doing the integration and the performance tests and some refactoring’s to the code,
so the data model could change slightly.
We plan to finish this by the end of the Month.
The next major release will contain the switch from CouchDB to PostgreSQL.

Our development branch for this is 'feat/couchdb-to-postgres-migration'. You can use this branch for testing the current state.
We have a docker compose stack in the directory 'docker/dev' to test the current implementation.
Next week we want to provide a docker image for the PostgreSQL branch.

If you have any further questions, please feel free to contact us

[rramos-xx]

LGTM for merging into main CouchDb-to-Postgres Branch. Then there we can do the corresponding updates to docs, unused methods, etc.