Use cases for nyssr.net

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. Its primary goals are modularization, flexibility, distribution, and scalability. The flexibility extends to the point where nyssr.net programs can run on a single node or within a node network consisting of hundreds of nodes. Additionally, a node network can integrate software, machines, and databases that are globally distributed and do not necessarily need to be hosted in the cloud.

You can build

Client-server software where the server is a node network.
Web applications composed of a large number of small services.
Application systems consisting of multiple applications that share modules, dialogs, and resources with each other – designed for large enterprises and government institutions.
Swing applications where the user interface runs locally, and the business logic resides in a node network.
and much more...

How do you proceed?

Extend your Java program

Integrate the Kernel library into your program to provide the core functionality.
By integrating the Kernel library, your program becomes a node.
Connect this node to additional nodes to form a distributed network.
Create services that function as plugins, which can be loaded by other nodes during startup.
Using this architecture, you can send messages to these services or receive messages from them.

Integrate local and remote databases

Start a node near your database to ensure efficient communication.
Create an API in JSON or XML tailored to your current requirements. Avoid attempting to build a universal service. You can create as many specialized services as needed, so focus your API on what is necessary for your immediate task.
Generate the message classes based on this API.
Create a service that processes the incoming messages and retrieves the required data from the database or writes data to the database.
Write the data into the messages, which are then sent back as replies to the request sender.
If this microservice needs to collect data for transactions, implement the service as a factory. Start a new target and return the address to the requester. The requester can then communicate directly with their target.
It doesn’t matter where the message sender is located or whether the database is installed in the cloud. You are operating within a node network.

Integrate local software into your system

Start a node near your local software to ensure optimal connectivity.
Create an API in JSON or XML tailored to your current requirements. Avoid attempting to build a universal service. You can create as many specialized services as needed, so focus your API on what is necessary for your immediate task.
Generate the message classes based on this API.
Develop a service that processes incoming messages and handles communication with the local software. All logic for interacting with the software should be contained exclusively within this service.
Write any received data into the messages, which are then sent back as replies to the request sender.
It doesn’t matter where the message sender is located or whether the software is installed in the cloud or locally. You are operating within a node network.

Retrieve data from external networks.

Create a service that establishes communication with the external network.
If you need to pull messages from this network regularly, use timers or the job engine.
Messages received from the network can be directly forwarded to other services or broadcasted to the node network.
Messages received via your service API can be forwarded to the external network.

Create new distributed web applications.

Create an application in the form of a small microservice.
Your first UI microservice should act as the entry dialog.
Additional UI microservices and UI nanoservices can extend and decorate the entry dialog.
Develop additional UI microservices that can be invoked on-demand.
Fetch the data presented in the dialogs from database microservices. Each dialog should have its own microservice for data retrieval and preparation.
Once created, UI dialogs can be invoked by other applications just as they are used by your initial application.
Scale your application rapidly. You can build applications with thousands of microservices. The effort required to operate these services will be no greater than if you only had a dozen.

Create server-based, distributed Swing applications.

Develop an application in the form of a small microservice.
The first Swing microservice should act as the entry dialog.
Additional Swing microservices and Swing nanoservices can be used to extend or decorate the entry dialog.
Create additional Swing microservices that can be invoked on-demand.
As a client, use a Java node with RemoteSkin plugins on the user's computer.
It is possible to run hundreds of different Swing applications simultaneously, even multiple instances, in a single virtual machine (VM). Additionally, multiple client nodes can be launched on the same machine.

Let us create your application for you.

If you currently have no capacity to create applications, contact us via e-mail.