SISnet 360 Technology
SISnet 360 is build with a proprietary framework, created 100% by us. From the data access layer and database connectivity to the integrations layer, based on SOAP and REST standards for the integrations layer and Java JDBC for the data access layer.
SISnet 360 is developed folllowing these requirements:
- It is built on the standardJEE6
- Uses the specification JSR 315 (Servlet 3.0)
- To be operative Java 8 is needed
SISnet 360 is compatible with any server that has servlet container capability that complies with the servlet 3.0 specification.
It is certified to run on the following servers:
- Apache Tomcat 8.5 or higher
- WebLogic 12c or higher
- WebSphere 8.5 or higher
- JBoss 7.2 or higher
- Wildfly 11 or higher
As database management systems (SGBD), SISnet 360 is capable of supporting any relational database that has a JDBC driver. It is currently certified for:
- Oracle 11g or higher
- DB2 8.5 or higher
- SQL Server 2012 or higher
- Postgres 10 or higher
Being independent of the system where the database is located, it can be deployed in PaaS, Amazon's Aurora Postgres or Microsoft's SQL Azure.
SISnet 360 is based on a layered model using the Model-View-Controller (MVC2) design pattern. Currently, the SISnet 360 model has three layers:
- Interface logic
- Business logic
- Data access
Business logic and data access layers are shared by the types of layer models used.
API Rest Model
This is the model to which the application is being oriented, and the most optimal one. It is developed in accordance with Zero Code paradigm and the JSON format is used for the communication of information.
Web Service Architecture
In Web Service Architecture, the simple command pattern is applied, meaning that, through rules, any endpoint of the system can be exposed.
Batch architecture is aimed at processing very large volumes of data, such as performing migrations.
SISnet 360 has 2 models to follow.
For the microservices architecture, SISnet 360 presents a framework where there is a core that is capable of executing the processing of all Zero Code elements. In this way, a microservice only contains the core that interprets this Zero Code and the configuration of rules that will execute the processing.
SISnet 360 has certified compatibility with Kubernetes, Google GKE and Anthos, Azure APPServiceand with RedHat OpenShift.
In a traditional deployment model which groups the functionality in a drop-down. It can be carried both in an OnPremises or Cloud scenario in IaaS and PaaS concepts, being compatible with both.