From 9969128d57e46a63dad5c4de402f3034e2e26229 Mon Sep 17 00:00:00 2001 From: cwtuan Date: Thu, 24 Oct 2024 15:14:45 +0800 Subject: [PATCH] fix link --- doc/manuals/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manuals/architecture.md b/doc/manuals/architecture.md index af0f2fb9..7a67d703 100644 --- a/doc/manuals/architecture.md +++ b/doc/manuals/architecture.md @@ -26,7 +26,7 @@ and MongoDB as the final database. Since the STH is a Node application and regarding the Web server, we opted for hapi as the module to use. Once again, we opted for flexibility and modularity over any other characteristic and hapi was the Web server which provided the best one (see [compare Express vs Hapi](https://strongloop.com/strongblog/compare-express-restify-hapi-loopback/) and -[npm compare Express vs Hapi](https://npmcompare.com/compare/connect,express,hapi,koa) for further information). +[npm compare Express vs Hapi](https://npm-compare.com/connect,express,hapi,koa) for further information). In the next figure we depict a high level view of the STH architecture including the concrete Web server and database currently used: