Understanding Service Board Architecture
The foundation for Service Board and its related applications is the Max platform. Max is a set of Cloud Foundry applications that implement a rapid application development platform as a service (aPaaS). Max uses PostgreSQL as its relational data store, and Elasticsearch for fast indexing and searching.
Service Board is developed on the Max platform to leverage the following:
• Entity framework APIs
• Scripting language support
• Process and rule engines
• User interface generation
• Design tools
• Application lifecycle management
• Package management
• Data import and export
• Security infrastructure
• Other Max services
Max Platform Component Architecture
Each Service Board tenant has the same basic deployment architecture, and is integrated with one unique Salesforce org. Tenants are isolated at runtime, with the per-tenant maximum system resource specified at provisioning.
Service Board Single-Tenant Deployment Architecture
Multi-tenancy implementations share no data, and the architecture is designed to avoid "noisy-neighbor" issues at the Cloud Foundry and OS levels. Tenant isolation also applies to data at rest, with dedicated data instances for each tenant that have unique access credentials generated by Cloud Foundry.
Service Board Multi-Tenant Deployment Architecture
For more information: