Non-functional Requirements

1. Security

Frontend

We use Cloudfront from Amazon Web Service, to protect our application from common attacks

  1. WAF (Web Application Firewall) – protection from the DDoS attack
  2. Signed URL – downloading the documents on the S3 storage bucket securely.

Learn More About Cloudfront from AWS ↗

Backend

We use JSON Web Tokens (JWT) to secure our API Server.

Learn More About JWT ↗


2. Performance

Cloudfront from AWS

Cloudfront service is a Content-Delivery Network (CDN), which means it can cache files to the edge location around the world, and clients can access those resources very fast.

Learn More About Cloudfront from AWS ↗


3. Reliability

Document Files

We use Cloudfront from AWS to improve the reliability of hosting the document server.

By using the S3 service and caching resources to the edge location, we are benefiting from their promise of high availability of their services.

Learn More About Cloudfront From AWS ↗


4. Usability

Simple UI

We are constantly reviewing our website designs to maintain high usability.

For example, to reduce the number of clicks from the users, we have decided to put all the related content into a single page view, but avoid information overloading for users.


5. Data Integrity

Hyperledger Fabric

A Blockchain framework for implementing the concept of decentralized ledgers, to make sure the data stored in the nodes are not altered by anyone.

By applying it to this project, we can make sure that all the transactions, delivery records, and documents are not altered by anyone.

Learn More About Hyperledger Fabric ↗