8Manage is 100% written in Java & JS and 100% mobile app and browser-based. Most private blockchain or private cloud enterprises run 8Manage as 3 to 4-tier systems. But 8Manage can be scaled up to run as N-tier systems such as the diagram shown below or scaled down to run on a single laptop. It is very powerful and flexible from a scaling up and scaling down standpoint.

The 8Manage server clustering design supports both real-time load-balancing and hot failover and has been tested to support up to 200,000 concurrent users on a private cloud installation.

All reporting in 8Manage can be performed in real-time, especially for blockchain information. 8Manage also supports a report server for BI type of analysis and reporting.

8Manage also supports SAN storage, Non SQL storage (e.g., Hadoop, Mongodb), backup facility and disaster recovery setup.

8Manage can be set up to support both public and private blockchains. For a public blockchain setup, the blockchain information stored in the enterprise’s storage is no more than the information stored in the public blocks. For a private blockchain setup, the blockchain information stored in the enterprise’s storage can be more than the information stored in the public blocks, but the extra information shouldn’t be affecting the validity of the information stored in the public blocks.

Unlike some enterprise systems that are written in multiple languages (e.g., ABAP/3, PL/SQL, RPG, Dexterity, MorphX, VB, C/C++) using different underlying technologies and run-time models, 8Manage is completely written in Java/J2EE and can be run on 32-bit or 64-bit Windows or Linux OS or VM. 8Manage supports Tomcat, JBOSS and WebLogic application servers and Oracle and SQL Server DBMS.

For interfacing with external systems, 8Manage supports the SOAP protocol and the Web Service interfaces. For legacy systems that don’t support Web Service, 8Manage can interface with them via RFC, RPC, Java RMI or file I/O.

8Manage technical standard is a reflection of 8Manage engineering team leaders’ experience and leadership to minimize the accidental complexity of the system level layer and maximize productivity for the application layer.

The following single-tenant architecture can be deployed with different configurations for different private cloud clients of different sizes.

We have deployed the following multi-tenant architecture for our public cloud clients. We put about 800 clients or 20,000 named users per cluster with the following configurations:

The following marketplace architecture can be deployed with different configurations for different market places of different sizes.

The marketplace system will perform real-time synchronization such as below in order to keep the global and local marketplace data in sync.