[
https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161367#comment-17161367
]
Andy Seaborne commented on JENA-909:
------------------------------------
For any small open source project, not "backed" by company, that's pretty much
the situation. A small number of people, each tending to focus on one part of
the system. Part of the "cost-effective" nature of open source software! It is
a bit multiplied by the fact that some of Jena's workflows used to end up with
the committers name in the log, not the contributor. We have got better at that.
RDF Delta has come along way since then (and did have some industrial contract
time to develop the cloud / no single point of failure version - which I would
point is an unusual for Jena!). But the principle of playing updates to all
servers is still there.
It gives horizontal scalability and high availability, for a system with modest
numbers of updates. It is not for high-update workload but triple stores like
Fuseki are more about publishing data than data gathering, i.e. reads are more
common than writes.
> Create Docker launcher for Fuseki
> ---------------------------------
>
> Key: JENA-909
> URL: https://issues.apache.org/jira/browse/JENA-909
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Andy Seaborne
> Priority: Major
> Attachments: Dockerfile.0, image-2019-10-02-22-24-12-723.png,
> log4j.properties
>
>
> Provide a Docker launcher and setup documentation for Fuseki2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
