Hardware Considerations

March 26, 2020 Contributors

The Momentum platform is designed to deliver high volumes of messaging traffic. This is accomplished through architecture that can be scaled vertically on all nodes and horizontally by adding nodes. When planning a Momentum deployment, you must understand both the physical hardware and the deployment environment. This section will help you determine the best deployment for the volumes you need to support, as well as the correct hardware for your current configuration and for expected growth.

Server Roles

Momentum is deployed as several distinct “roles”, each providing different functionality of the Momentum Solution. The available roles are:

  • Platform Role

    • MTA – Supports all Message delivery functionality including Adaptive Delivery. Optionally, also supports Message Generation.

    • Platform DB – Stores all templates, recipient lists, and generation task data.

    • Event Hose – Distributes all system events to the Analytics node and Webhook subscriptions.

  • Analytics Role

    • Analytics DB – Stores aggregated data of all system events delivered by the event hose.

    • Web User Interface – Provides graphical reporting summaries, template editing and management, recipient list storage management, and authentication key generation and management.

    • HTTP Proxy Service – Supports all REST API including message generation, administration, and metrics (reporting) functions.

Note

You do not need to install all roles. Also, some sub-roles can be deployed on separate nodes. Listing all possible permutations is not feasible. Please consult with a Momentum Product Manager for more information on highly distributed deployments.