![Cover image for [Apache Superset] Topic #2, Superset ARCHITECTURE](/image.pl?url=https%3a%2f%2fmedia2.dev.to%2fdynamic%2fimage%2fwidth%3d1000%2cheight%3d420%2cfit%3dcover%2cgravity%3dauto%2cformat%3dauto%2fhttps%253A%252F%252Fdev-to-uploads.s3.amazonaws.com%252Fuploads%252Farticles%252Fuy6uy0jns15v5xzj0409.png&f=jpg&w=240)
Hello, it's me again - Duc Nguyen (Duke)
In the previous part, we talked about theconcept, how to install and launch Superset, if you haven't seen it, clickhere
Today, let's talk about themost important topic to mastering Supersets - ARCHITECTURE!
Superset 4.0.2
has the following main modules:
1.Superset application2.Metadata database3.Worker4.Beat5.Caching
First, so what's the purpose of Superset application?
Superset application is acore component, included thePython (Flask)
(backend), API layer andReact
(frontend)
How about the Metadata database?
It uses for store chart definitions, dashboards, user information, logs, etc with thePostgreSQL
andMySQL
supported
How about the Worker?
- Execute asynchronous tasks
- Run asynchronous queries
- Send emails
How about the Beat?
- Acts as a scheduler
- Specifies the time for workers to perform their tasks
In short,Worker
andBeat
work together with the caching layer, using it as a message broker to coordinate tasks.
How about the Caching?
- Cache query results to speed up and reduce load on the data warehouse
- Act as a message broker for workers
- Usually uses Redis
Do you have any questions? Let's wait for the next topic to guide you on how to explore and visualization data.
Top comments(0)
For further actions, you may consider blocking this person and/orreporting abuse