We use email for almost every kind of digital and non-digital notification. Why should it be complicated to provide your system with a robust email delivery system? What if this system provided support for templates, multiple sends, send notifications, return receipts and resend in case of error? Here is the famous Email Module, used for years in mission critical systems!

Email Module :: Key Features

• Sending emails with attachments
• Bulk email sending based on templates, both for email text and attachments
• Manage multiple users for mailings with different roles
• Monitor queued emails
• Send emails in the future! Delayed emailing functionality allows you to schedule the sending of one or more emails without sending them immediately.
• Supports SSL and PEC
• Robust, robust, used for years in mission critical systems

There is no point denying it, sooner or later all users will ask for an MS Excel export for their data. The Excel Module allows you to respond quickly and proactively to this need.

Excel Module :: Key functions

• Allows to generate Excel files from a structured JSON
• Supports all elements of formatting and formulas
• Supports the generation of multiple worksheets in a single workbook
• Supports Sparkline chart generation.
• Extremely fast, even for large Excel files
• Does not require MS Excel on either the client or the server

Do you really want to decouple the components of your system and/or communicate with other systems effectively and efficiently? No, polling and/or shared data storage are not the right way.

The Event Streams module (available in DMSContainer 4.0.x) will allow you to solve all integration and notification problems between heterogeneous systems. Communicating using push notifications will no longer be complicated and difficult, but will become a simple and efficient way to elevate the basic architecture of your software solution.

EventStreams Module :: Key Features

• Send messages to one or more queues, also in a transactional way
• Integrate heterogeneous systems without creating dependencies that dirty the system architecture (e.g. Desktop/Mobile or Web/Mobile)
• Allows a system component to perform operations in response to an event generated by any other system component
• Implement advanced “Queues Purging” systems to avoid space problems
• Listen for and react to “events” generated by microservices hosted by DMSContainer
• Listening to and reacting to events generated by external systems integrated with DMSContainer.
• It offers ready-made solutions for the most common cases and is very easy to use.

“There is probably no non-trivial system that cannot benefit from the EventStreams Module.” – quote A User

One of the most common situations in distributed systems is that of having a shared resource; a database record, an invoice, an order, a generic aggregate-root, a file, a hardware device, a log file etc. In short, in all situations where it should not be possible to start modifying an entity if someone else is already modifying it, the SynchUtils module is the solution!

The Synch Utils module (available in DMSContainer 4.1) allows you to solve all synchronization problems between distributed systems that share access to a shared resource.

SynchUtils Module :: Main Features

SynchUtils handles locks of exclusive type. With this type of lock (conceptually similar to the CriticalSections offered by operating systems) it is easy to implement the design pattern called pessimistic offline lock. This type of design pattern prevents simultaneous updates of resources in charge of the system.

• The resources could be records, files, complex structures (graphs) or anything else that could be concurrently read and/or modified by more than one client.
• SyhcUtils' exclusive locks are distributed and accessible via a convenient JSON-RPC API.
• When a user wants to update a shared resource, they attempt to acquire a lock; if they do acquire a lock, no other user will be able to modify the same resource until the lock is released or expires.
• An advantage of the pessimistic lock model is that it avoids the problem of conflict resolution by preventing conflicts from occurring.
• Updates are serialized and each subsequent update starts with the changes made by the previous user.
• It offers ready-made solutions for the most common cases and is very easy to use