PoC: Fractal Service (load balancer) #536
Draft
+532
−0
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.
Fractal Service
By tracking database query targets. Create short lived caches (using
@cap-js/sqlite
) which all instances redirect their queries to. Creating a live cache which can be queried reliably. Greatly reducing the load on the underlying database. While also greatly increasing query response times overall.With the capability to integrate the load tracking with the BTP load balancer custom metrics. Allowing the creation of new application instances when heavy application loads are detected. Removing the local cache limits inherited from the application memory allocation.
Example
Local
SQLite
cache vs pure locally hostedPostgres
.Diagram
Diagram demonstrating how the queries are tracked and the cache is utilized by multiple application instances.