Easy-IPv6 ArchitectureEasy-IPv6 Architecture

Easy-IPv4 was based on a 2-tier architecture. This meant that the client applications connected directly to the database. As the applications became more complex we recognised that we were growing out of our architecture.

The decision was made to rebuild Easy-IP using a multi-tier design. In the new design client applications connect to the Easy-IP Server which in turn connects to the Database.

As the business logic is now found solely in the Easy-IP Server we have had been able introduce many features that were not possible in previous versions of Easy-IP:

  • Subnet/IP Address Integrity - All changes to the Database must go through the Easy-IP Server. This means that only valid changes can be made.
  • Speed - Previously clients connected directly to the Firebird Server. Unfortunately, the Firebird network protocol is quite 'chatty' and could be very slow over connections with high latency. The protocol used between the Easy-IP Server and it's clients is a highly optimised binary protocol that incorporates compression or encryption (optional).
  • Centralised files and settings -The majority of user files and settings are stored directly on the Easy-IP Server. Administrators can now control their users' experiences centrally.
  • Change Control - Change logging is now built right into Easy-IPv6. Administrators have the ability to control which field changes are logged and how long logs are kept.
  • Plugable authentication - User authentication is now controlled by the Easy-IP Server rather than the database. This enables additional authentication methods in the future.
  • Database - Easy-IPv6 uses a Firebird Database, but additional database types can be added to future versions.
  • API - Users can access the Easy-IP Server via the new API. You can write your own client software that interfaces with Easy-IP.