FAQ nyssr.net

I have a server software. How do I get started?

Include the nyssr-net JAR as an external library.
Initialize the micro kernel.
Create a package and initialize it with a service starter.
Create a target and register it.
You are now ready to send messages to your nyssr.net.
To do this, create a new node.
Create a plugin with a microservice.
Load the plugin into the second node.
Send a message from your server software to your microservice and catch the response.

How many nodes do I need to start with?

You can start with one node in any case.
You can create and test your microservices, as well as the code that will use those services, in a single node. Later, you can add more nodes and then load and run the microservices on other nodes. In any case, you can develop and debug everything with a single developer workstation. We work with IDEA, and we can conveniently use it to start multiple nodes, set breakpoints, look at variables.

What are active microservices?

Active microservices have their own status. Many of you have your own workflow, and need to send and receive their own messages to do the job.

For example, many microservices are dependent on user permissions. With the request they receive a session token, which they must check for actuality and user rights. To do this, they send messages to the session management before the job itself and analyze its response. If everything is correct, they continue with the current task.

Often, these microservices are also factories. For example, if a RemoteSkin dialog is requested, the factory starts a target owned by the requester. If the requester is terminated, it ensures with a message that the dialog instance is shut down. If the requester node and thus the requester dies, the service is notified by the system and automatically terminates the service instance.

In each case, the service instance has its own state and also participates in messaging (communication with the client, requester and other objects).

nyssr.net is the nicer net