FrankChen021 commented on issue #12262:
URL: https://github.com/apache/druid/issues/12262#issuecomment-1059984018


   > At that point, a small Druid cluster would be pretty simple: just a 
Coordinator and this new process type (or a few of them for scale-out)
   
   This is a big advance for Druid that addresses the pain point of current 
complex conceptions and deployment. One of the reasons that many people now 
prefer ClickHouse as their analytic DBMS is its simplicity, they only have to 
download one process and start it and then they can import data and query.
   
   I'm also wondering if the core of Druid is combined into one process, is it 
possible to make Druid a built-in component, like an embedded database system, 
for other systems to integrate? I have this idea because we're using Druid to 
store application metrics, but for Druid's own metrics, they're emitted into 
other time-series database like prometheus. 
   If Druid can store its own emitted metrics by using its own storage and 
query capability, it can greatly simplify the operation.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to