|
| Evaluation Criteria | h | Justification |
| p1 | Database per service | 1 | DBMS developers provide the necessary drivers to connect to their servers. JAVA being very popular, these drivers are available. |
| p2 | API Composition | 0 | No implementation available |
| p3 | SAGA | 0 | No implementation available |
| p4 | Domain Event | 1 | The events are managed thanks to the ActiveMQ service whose driver is available. |
| p5 | Event sourcing | 1 | Events are handled by the ActiveMQ service, whose driver is available. |
| p6 | Testing of service components | 0 | No implementation available |
| p7 | Service Integration Contract Testing | 0 | No implementation available |
| p8 | Multiple service instances per host | 0 | The deployment is done in a software server and only one instance of the server can be launched. Moreover, the software runs on a port. |
| p9 | Service instance per container | 1 | Software can be launched in a container. |
| p10 | Serverless deployment | 1 | A JAVA EE software can be deployed without a server. Because all dependencies can be loaded on a repository. |
| p11 | Externalized configuration | 0 | No implementation available |
| p12 | Remote Procedure Invocation (RPI) | 1 | JAVA native remote procedure calling techniques are available. |
| p13 | Message exchange (Messaging) | 1 | JAVA EE, has an API, JMS for message communication. |
| p14 | API Gateway | 1 | JAVA EE, allows the implementation of REST API. |
| p15 | Backends for frontends | 0 | No implementation available |
| p16 | Service Registry | 0 | No implementation available |
| p17 | Client-side service discovery | 0 | No implementation available |
| p18 | Server-side service discovery | 0 | No implementation available |
| p19 | Self-registration | 0 | No implementation available |
| p20 | Circuit breaker | 0 | No implementation available |
| p21 | Access token | 1 | Token-based API security is available. |
| p22 | Log aggregation | 0 | No implementation available |
| p23 | Implementation measures | 1 | Software control is done through the software server. |
| p24 | Distributed tracing | 0 | No implementation available |
| p25 | API Health Check | 1 | The software is controlled through the software server. |
| p26 | Composition of the page fragment on the server side | 1 | Thanks to JSPs, we can compose fragments on the server side and make a view functional. |
| p27 | Composition of the client-side user interface | 0 | JAVA EE, is server only. |
| Total | h = 1, 12 times & h = 0, 15 times | ||