Skip to content
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.

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

[Architecture] Improving Cache Loading & Seperating Metaversefile.import from React. #2239

Open
utf94 opened this issue Jan 21, 2022 · 0 comments
Assignees

Comments

@utf94
Copy link
Contributor

utf94 commented Jan 21, 2022

Our current architecture is taking a lot of time in loading and caching based on the machine and this is effecting our caching strategies with caches being invalidated and all in order to solve this problem out an over view of architectures are attached below

image

It is proposed that we will seperate the Metaverse-file import entirely from the React application while still keeping the react refresh in the vite.config we will remove the rollup.config from vite and will actually change it to an entirely new implementation called as Metaverse-Server. the Metaverse-server will be composed of the functionality of rollup in iteself and will provide the option to compile the modules using Just in time compilation mode. Using JIT will let each user have their own cache that will be invalidated in X hours of time.

The two functions which will be impacted by this are:

image

In this architectural change

  • No changes are required in Totum
  • No changes are required in React
  • Instead a simple branch out will happen when the index.mjs recieves the import request this is where the Just in Time compilation will happen.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants