Architecture
Technical mySync DM architecture is designed to be very flexible. Smart flexibility allowed us to make the system also scaleable and robust. This means our customers can start from small workstation class server, continue with virtual machine or single server installation and to go up to multiple physical server setups.
There are some example setups later with example user amounts.
On the server-side mySync is mostly Java. Currently mySync is supported on Linux.
High-availability and scaleability
As just a single server host is easily powerful enough to handle all but the highest installations, high-availability (HA) is really more important aspect than the traditional scaleability. Simplest and most common form of HA is a dual server solution.
When the user count goes to tenst of thousands of users, or more, both the push-mail component server, and web portal might require some boost in the form of an additional server host. Additional server hosts can easily be added to a HA solution when needed. Same goes for other server roles in the solution.
Schematic view of the full ecosystem.
Web portal, or WebUI
mySync DM web portal is the central point of action. It is used by all user classes, including vendor, organisation manager, and end-user. Each user class has a different view to the system, as they have different roles and set of data to manage.
Technically the portal interacts with the LDAP data store, not with the component servers (including data synchronisation, device management, mobile network gateway, push-mail). One could see the portal as a mere LDAP editor. In a way it is that. Because LDAP is at the very core, it makes the web portal the most important visible part of whole mySync.
On the client side the portal only uses HTML, CSS, and JavaScript.
This makes the requirements quite light.
More indepth view of the mySync architecture.
The data store
Basically all of the data, both device management, and data synchronisation is stored in OpenLDAP. Latest OpenLDAP allows for:
the fastest possible data store,
very scaleable and highly available data store with multiple masters, etc.,
nice optional integration to other LDAP-based products, such as Microsoft Active Directory, and Lotus Notes/Domino,
architecturally the most appropriate data store for this kind of application, and
customised, optimised, and yet compatible schema.
LDAP is our strategic differentiator and one of the technical innovations.
Schematic view of the mySync with optional and external components.
Web service
Web service is considered a must in modern service product. We have implemented implemented web service with a twist: big/important enough customers get to define the web service to suit their need. For others we have the standard interface with equal functionality.
Otherwise, the most important tasks done via web portal, can also be done via web service over http or https. There is nothing magic here.
Redundant dual (SMS and TCP/IP) connection from mySync to mobile device; both can be multiplied.
Collaborative features
mySync extends traditional data synchronisation solutions with unique collaborative features, such as company common addressbook, or conference room. Those features are controlled by the portal.
Company common addressbook is a common example. It is also very practical example, as properly implemented, is saves a bundle for every organisation using it. Nice thing about the mySync mplementation is, that the addressbook is replicated to all company users, which have at least read rights to the resource.
mySync does not stop here. We've also implemented for everybody within and organisation a feature to selectively share contacts, calendar, notes, and tasks to share those items to collegues. Sharing is done either read-only, or read-write. We understand this feature is not for everybody.
Having collaborative features without product like Microsoft Exchange, Lotus Notes/Domino, or Novell Groupwise, with just standard OMA DS (SyncML), our web portal, and the mobile devices, is an industry first by mySync.
Some example setups and rough initial capacity planning
Note: Below mySync Express alone has equal requirements to mySync Management with mySync Express, so it is not disclosed separately.
1 - 1 000 000 users, mySync Management only, single-server, no HA, no LB: anything goes here hardware-wise. There are no limitations, both physical and virtual server works. Mobile terminal is usually used, and it causes careful planning when going virtual. Server memory between 2 GiB and 8 GiB depending on the amount of users. Reserve 1 MiB disk space per user to be on the safe side.
1 - 1 000 000 users, mySync Management only, dual single-server, HA, no LB: anything goes here hardware-wise. There are no limitations, both physical and virtual server works. 2 mobile terminals are usually used (one on each server), and it causes careful planning when going virtual. Server memory between 2 GiB and 8 GiB depending on the amount of users. Reserve 1 MiB disk space per user to be on the safe side.
1000 users, mySync Management and mySync Express, single-server, no HA, no LB: anything goes here hardware-wise. There are no limitations, both physical and virtual server works. Mobile terminal is usually used, and causes careful planning when going virtual. Server memory 3 GiB. Reserve 5 MiB disk space per user to be on the safe side.
50 000 users, mySync Management and mySync Express, dual single-server, HA, no LB: real server hardware is required. There are no limitations, both physical and virtual server works. 2 mobile terminals are usually used (one on each server), and it causes careful planning when going virtual. Server memory 8 GiB. Reserve 5 MiB disk space per user to be on the safe side.
100 000 users, mySync Management and mySync Express, dual single-server, HA, LB: real server hardware is required. There are no limitations, both physical and virtual server works. 2 mobile terminals are usually used (one on each MNG server), and it causes careful planning when going virtual. Server memory total 12 GiB. Reserve 5 MiB disk space per user to be on the safe side.
10 000 000 users, mySync Management and mySync Express, multiple servers, HA, LB: real server hardware is required. There are no limitations, both physical, virtual, and mixed servers works. multiple mobile terminals are usually used (one on each MNG server), and it causes careful planning when going virtual. Careful planning required due to high number of users. Reserve 5 MiB disk space per user to be on the safe side.
Recommended implementation of scaleable load-balancing (LB) high-available (HA) solution; alternatives exist.