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

✨ Architectural Redesign #179

Open
uberroot4 opened this issue Nov 3, 2023 · 0 comments
Open

✨ Architectural Redesign #179

uberroot4 opened this issue Nov 3, 2023 · 0 comments

Comments

@uberroot4
Copy link
Member

uberroot4 commented Nov 3, 2023

Each visualization should be implemented as plugin, similar to apache/superset.
Following proposed structure, similar to plugins

  • Frontend & Backend should be split into two parts
    • e.g. frontend: binocular-frontend
    • e.g. backend (indexing part) binocular
  • each visualization should be located in <frontend-root>/plugins/<visualization-name>
    • each visualization is its own "project", i.e. has its own package.json
    • binocular-frontend uses the visualization in the package.json in the "dependencies" section
      • e.g. "@superset-ui/plugin-chart-echarts": "file:./plugins/plugin-chart-echarts"
  • Can the backend indexers also be structured in a similar way to be more efficiently extendable?
    • Or even replaceable? I.e. to replace the current node implementation with e.g. rust/python/wasm/etc. without much restructuring
    • What is necessary for this step? How does e.g. models need to be defined to be universally useable?
@MaximilianZenz MaximilianZenz changed the title Architectural Redesign ✨ Architectural Redesign Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant