https://sillysky.net/home-articles/ Recent content in Home Articles on sillysky.net Hugo -- gohugo.io en Mon, 20 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/non-cloud-based-web-applications/ Mon, 20 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/non-cloud-based-web-applications/  Real distributed micro frontends on mesh of nodes with RemoteSkin Almost no HTTPS The web server of a node delivers a static HTML page, and then it goes back to sleep. All further content is loaded via a WebSocket connection, not HTTPS. Almost no Cloud The node with the web server plugin is installed in the cloud. The other nodes can run apart from the cloud so that the applications, the microservices and the databases can also run "at home". https://sillysky.net/home-articles/home-asynchronous-design/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-asynchronous-design/ nyssr.net is composed of a mesh of Java nodes. Each node can load hundreds of services as plugins. Services communicate asynchronously via messages, making almost all processes in nyssr.net asynchronous. nyssr.net does not waste resources on waiting. Sending messages is asynchronous, the response will come back at a later time. Since everything happens in parallel , CPUs and cores are also completely utilized. Or the other way around: Even small computers with several cores perform as much as otherwise much larger and more expensive units. https://sillysky.net/home-articles/home-bidirectional/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-bidirectional/ nyssr.net enables adhoc bidirectional communication with every object in the network. No configuration is required for this. The recipient also does not have to register for specific messages. nyssr.net uses multi-directional communication for its services. This means that messages can not only come back from an addressed service (bidirectional), but responses can also come from other services. A asks B, B sends the message to a corresponding service on another node, and the service replies to A. https://sillysky.net/home-articles/home-configure-nodes/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-configure-nodes/ How do you configure nodes in a mesh node network that are located behind firewalls, i.e. are not directly accessible via SSH? Via the node network itself, of course! After selecting a node, the “NodeManager” web application offers to change the configuration of the corresponding node. There are two options here: Changing the settings in the Java preferences used by the node: Edit Java preferences of a remote node Changing the configuration files that are read out when the node is started, and whose values are entered in the Java preferences: Edit configuration files of a remote node https://sillysky.net/home-articles/home-plugins/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-plugins/ nyssr.net is a network of interconnected Java nodes using TCP channels to facilitate message exchange. Messages are routed through these channels, avoiding the need to establish new connections dynamically. A mesh of nodes, some in the cloud, others outside Each node is built around a nimble and quick-loading micro-kernel. This micro- kernel loads additional functionalities in the form of plugins during startup. Remarkably, even essential features like TCP or the transport layer are loaded as plugins, alongside various services and applications. https://sillysky.net/home-articles/home-evergreen-software/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-evergreen-software/ Non aging software We all know software that has grown until it could no longer be maintained or rebuilt. At least not at a manageable cost. We know many companies that, in addition to the team for the further development of their productive software, have one or even more teams to build alternatives. The larger a monolith becomes, the smaller the chance of fundamental change. This is different for small modules that are only loosely coupled. https://sillysky.net/home-articles/integrate-local/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/integrate-local/ Why can nyssr.net integrate local services behind firewalls? Access nyssr.net is a network of interconnected Java nodes using TCP channels to facilitate message exchange. Messages are routed through these channels, avoiding the need to establish new connections dynamically. A node started behind a firewall can easily connect to another node in the cloud. All connected nodes are visible to each other. All nodes are treated equally, regardless of where they are executed. https://sillysky.net/home-articles/home-session-management/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-session-management/ nyssr.net has integrated session management with associated user, role and rights management. Virtually all operations in the node system can be secured with appropriate rights. The application for managing users, roles and rights is available in two versions: “RemoteSkin for Web” and “RemoteSkin for Swing”. UserManager application for the web Function In our applications, a login is always required first. The login dialog is therefore the first dialog displayed. After a successful login, a second application is shown for selecting the target application. https://sillysky.net/home-articles/home-java/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-java/ We use Java 8 for development, but we can deliver the kernel and plugins in all newer Java versions. An email or a request in the forum is sufficient. Reflection We use Java in its simple form, i.e. we do not use reflection for performance reasons. Third-party libraries We use practically no third-party libraries in the kernel. This allows us to avoid dependencies on other developers. In most cases, we only used small parts of the libraries used anyway. https://sillysky.net/home-articles/home-make-use-of-mesh/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-make-use-of-mesh/ A mesh network offers several advantages over star-shaped structures: Nodes Each node is typically connected to multiple other nodes, forming a mesh-like structure. Messages are forwarded through these links between nodes to reach their destination. All links between nodes are continuously monitored, and latency is measured in real time. This allows the routers on each node to gather the necessary information on which path a message should take to reach its destination the fastest. https://sillysky.net/home-articles/home-service-resolution/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-service-resolution/ nyssr.net supports a service resolution that requires no configuration. This is the reason why thousands of services can work together in a node network in nyssr.net without burdening developers. Automatic load balancing and the automatic discovery of microservices are vital features on nyssr.net. The microservice registry handles both of these services, making it the central heart of the network. If the node hosting the microservice registry fails, it could lead to a significant disruption in the network. https://sillysky.net/home-articles/home-performance/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-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. https://sillysky.net/home-articles/home-technical-overview/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-technical-overview/ This page gives you a technical overview of nyssr.net. The Net nyssr.net is a network of Java nodes that are interconnected via TCP channels. Messages are transmitted through these channels. The Node A node consists of a small 1.3 MB kernel, which loads additional functionality through plugins. A single node has the capability to load hundreds of plugins. Plugins Plugins are usually small JAR files that provide services for the network. https://sillysky.net/home-articles/use-cases/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/use-cases/ nyssr.net is well-suited for developing a wide range of Java software. You can use it to create innovative software or extend your existing software with entirely new capabilities. There is no need to build everything from scratch. You can iteratively create services and expand your programs step by step. This allows existing software to be gradually and seamlessly migrated to nyssr.net. nyssr.net is designed specifically for the development of network-based software. https://sillysky.net/home-articles/home-web-applications/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-web-applications/ Web applications that use nyssr.net work completely differently than we are used to. This also opens up entirely new possibilities, such as distributed applications, load balancing at the dialog level, high performance, and more. How can web applications with nyssr.net be categorized? Web applications under nyssr.net consist of distributed Micro UIs and Nano UIs. They are made up of small services executed across a network of nodes. The frontend modules are completely independent from one another, just like the backend services. https://sillysky.net/home-articles/home-lib/ Wed, 15 Oct 2025 00:00:00 +0000 https://sillysky.net/home-articles/home-lib/ By integrating a small library, your application or microservice becomes a node. You can then publish and use any services and send messages to other nodes. Any Java program can mutate into a nyssr.net node by including the kernel JAR. We've made this easy for you. Java Version nyssr.net requires Java 8 or higher. Dependencies The following third-party libraries are used: Library Vendor Size in KBytes annotations JetBrains 19 json-simple Google 24 Together, that's just over 40 KBytes (!