jLupin Next Server
  • Entering the world of microservices hasn’t been so easy!
  • Increase your efficiency, enable 24/7, reduce TCO…
  • … keeping the architecture simple and scalable!
play video

JLupin Next Server basics

JLupin Next Server – what is it?

JLupin Next Server (JLNS) is a Java application server which runs applications as seperate JVM processes and provides high performance communication protocol between them (as well as for external systems and layers). These applications are sets of ordinary Java classes in jars files, controlled through Spring IOC (default application container for JLNS). Applications on JLupin Next Server are called Microservices, because their business logic are automatically available as services through various communication protocols:

  • JLupin Java Remote Object Invocation (binary)
  • Web Service http – XML
  • Web Service http – JSON
  • JLupin Asynchronous Queue (binary)

JLupin Next Server key features

    Highest application availability

    On JLupin Next Server each application is separate OS process
    with own memory allocation.
    Unavailability of one application does not affect operation of other.

    Share Fast as Possible Business Services By Variety Of Transfer Protocol.

    Share Business Services by variety of transfer protocol (JAVA-OBJECT, WEB SERVICE-SOAP-XML, WEB SERVICE-HTTP-JSON) synchronous and fast asynchronous).

    No additional deployment descriptors or annotation in JAVA CODE.

    SEE JLupin WEB SERVICE-SOAP-XML-FACADE PATTERN and WEB SERVICE-HTTP-JSON FACADE PATTERN

    Low Infrastructure Costs. Use Free JLupin`s Software Load Balancers.

    Use Free JLupin`s Software Load Balancers which can be parts of client application to direct traffic on proper server node.

    Protection against unavailability or overload of subsystems.

    Separate Named Thread Pool for execute business services.

    Completely on-line and very safe change application version process.

    Completely on-line and very safe change application version process (with executing all started requests in old application) based on switching request movement between OS process (upgrade and downgrade on demand).

    Automatically increasing application memory in case of memory overflow.

    Increasing application memory in case of error for example OutOfMemoryError or StackOverflowError with full availability of applications

    Write application with ease. Default integration with Spring IOC

    Use the power of the Spring IOC Container

Learn more about JLupin