Performance
- File size
- The kernel is only 1.3 MByte in size and therefore very fast to load. One consequence of the small size and significant asynchronicity is the rapid startup of the node. A central system node, incorporating various central registries and TCP servers, launches in approximately 200 ms. This is achieved even though about 400 dependency resolution jobs are executed at startup.
- Microservices are usually only a few Kbytes in size. They are therefore loaded very quickly. There is no overhead (web server etc.). One node can load hundreds of services.
- The entire network can be rebooted within a few seconds.
- Messages
- Messages are streamed and not parsed. This means that no JSON or XML is used. This gives you an advantage in terms of speed and resource consumption.
- Message size
- Messages vary in size depending on what they are transporting. Simple notifications are smaller than 100 bytes. Example: All messages to display the Swing application “UserManger”, including the description of the main dialog, together comprise about 40 KBytes.
- A simple flag in the message header ensures automatic compression of the payload, which further reduces the message size, especially when transporting texts.
- Open TCP channels
- Messages are transported between nodes over open TCP channels. This eliminates the need to establish a connection with a security handshake. Communication via open channels between nodes ensures very short latency times. This allows you to easily and conveniently use services across multiple applications, maintaining and deploying them separately from the applications.
- Asynchronous messaging
-
All messages in
nyssr.net are asynchronous. There is no waiting for a response at any point. - Distribution
- Distributed systems can perform tasks faster than centralized systems by distributing the workload across multiple nodes. This reduces the time required to perform tasks and increases the overall efficiency of the system.
Conclusion
These properties ensure that high performance is achieved for applications even with low bandwidth. This applies to web applications as well as server-based Swing applications.