Hyperledger-Composer：为什么使用 Node.js 而不是 Angular？

Question

When developing Hyperledger Composer applications, there is a typical solution architecture that looks as follows:

According to the docs there is an alternative solution architecture that uses Node.js (seehttps://hyperledger.github.io/composer/latest/applications/node ):

Why would one choose the second architecture (with node.js), given that this involves one step more: not only do you have to write a node.js application but you then also have to develop a front-end for this node.js application (so 2 steps).

In the case of the first architecture, one only has to create an Angular application (because the REST server just needs to be started but the REST API is generated automatically by the framework) and is done (so there is only 1 step).

Are there any arguments in favour of using Node.js I'm not seeing?

Answer 1

The case for node.js is only if you don't want to create a user interface, or, if you wish to create wrappers around the existing hyperledger endpoints that reformat the consumption. A case could be that every day at 5pm you want to post an update to an asset based on what has changed in a different database somewhere... in this case you couldn't use Angular directly.

It's also important to note Angular is exclusively client side, Node.js is exclusively server side, and you cannot serve an API with Angular.

Separation of front end and back end is common practice now and is suggested for applications that contain both. Here's an article on it: https://quickleft.com/blog/six-reasons-we-split-front-end-and-back-end-code-into-two-git-repositories-working-with-github-repositories/