During initial development we are starting out with bundeling our angular app with the api by serving the angular app as dropwizard assets. There we use webpack-dev-server in proxy mode for easier development with livereload.
We don't like the complexity of seperation from the start. If we run into problems (assets need to scale differently than the api) it's pretty easy to extract the static angular app and serve it via a separate webserver.
even if the hole knowledge graph would be filled out by humans, there would still be errors in it, thats just how it works with this sort of big data. No way you could design a computer algorithm which does this job without a single error
