** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
The choice of protocols and message formats can have a significant impact on energy consumption during data transfer. Some protocols are more efficient than others because they use less data for overhead (such as headers) and can achieve the desired level of communication with fewer bytes transferred.
For example, HTTP/1.1 opens a new connection for each request/response pair, which can be inefficient. HTTP/2, on the other hand, allows for multiple requests and responses to be multiplexed over a single connection, reducing the overhead and latency associated with establishing connections.
Similarly, message formats like XML can be verbose compared to more compact formats like JSON or binary protocols like Protocol Buffers (protobuf), which can further reduce the amount of data transmitted.
### Choosing HTTP/2 and JSON for a Node.js Server
For this example, let's create a simple Node.js server that uses HTTP/2 and JSON for efficient data transfer.
