MODSOURCE-664 move flattening of parsed records into the module #556
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # mod-source-record-storage-server/src/main/resources/liquibase/tenant/changelog.xml # mod-source-record-storage-server/src/test/java/org/folio/rest/impl/RecordsGenerationTest.java # mod-source-record-storage-server/src/test/java/org/folio/rest/impl/SourceRecordApiTest.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Improve reliability of the database to handle more concurrent requests & more efficient processing of incoming source records when scaling up more instances of SRS.
Approach
We need to lift a bunch of processing out of the database where feasible. Flattening a parsed record in a module instance instead of the database will be a step in the right direction. This will allow the expensive flattening processes to be executed on cheaper & more scalable compute platform and free up the database to focus on persistence for domains of FOLIO.