Related links
Framework Core functionality
- Client-defined object attributes
- Common Libraries
- Default server methods
- Export collection of objects
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- Import collection of objects
- Multi tenant Architecture
- Strings and translations
- Event-based architecture
- System messaging
- User sessions
- User defined fields
Libraries & Lincences
Module - support for management
Front-End Scripting
System Management
Task Management Module
Task & Task pattern
Mobile & Web Application
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- clientprogramming_fevalglobal
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
Mutli-tenant architecture
AyMINE is modern system since the design root proposed to work in SaaS model for many clients
The multiclient ahrchitecture was proposed in order to serve perfectly in the SaaS model. Thanks to that, its SaaS provision is much simpler than for most of the application desinged for single-company used.
The major multi-client principles
- All clients have data in the same scheme but they are completely splitted
- All SQL views are always linked to the client
- The data and application wall between the clients' space is managed by the AyMINE framework. Developers to not bother about that. It stronly reduce risk of error made by programmer
- Application server processes always runs for single client only
- User application don't see anything about the client definition. It can never skip to another client
It has also some implications to the usage
- Users cannot build up their own SQL queries. Since there are not only their data, self-defined query is always i potential penetration over the wall
- Many counter and pre-defined values are system-defined and clients cannot update them easily. However, there is roadpath how to make them country-related or even customer-related. Thus, it does not hinder customer-related solution when delivered by responsible programmers.