[
https://issues.apache.org/jira/browse/DL-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477221#comment-15477221
]
Leigh Stewart commented on DL-38:
---------------------------------
Its something we've considered playing with - essentially co-locating a proxy
process with each bookie.
This would simplify deploys, but you also lose the advantage of independent
scalability of proxies and bookies. From perf perspective proxies still have to
talk to other non-co-located bookies so its hard to say, but probably no worse
than Kafka replication.
One thing that has been suggested is using this as an entry-level deployment
option, and allowing people to switch to decoupled deployment as their needs
change.
> Running write proxy together with bookie
> ----------------------------------------
>
> Key: DL-38
> URL: https://issues.apache.org/jira/browse/DL-38
> Project: DistributedLog
> Issue Type: Task
> Components: distributedlog-core, distributedlog-service
> Reporter: Khurrum Nasim
> Fix For: 0.4.0
>
>
> We'd like to explore the possibility of running write proxy together with
> bookie. Any guideline?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
