HiltonMTG: 05061988 @dotcms

Multi-Server Architectures

chris.mccracken@dotcms.comjason.tesser@dotcms.com

Multi-Server Architectures

• Determining Your Needs

• dotCMS Architectures

• Enabling Technologies

• Pros and Cons

Multi-Server Architectures

Multi-Server Architectures

Determining your needs

Fault Tolerance

• dotCMS

• Database

• Assets

• Scope of fault

Multi-Server Architectures

Determining your needs

Capacity Management

• Request Volume

• # of Hosts/Contentlets

• Surge flexibility

• Frontend vs Backend

Multi-Server Architectures

Determining your needs

Client Latency Optimization

• Geographic

• Network

Multi-Server Architectures

dotCMS ArchitecturesClustering (shared database/assets)

Multi-Server Architectures

dotCMS ArchitecturesPush Publishing (shared nothing)

Multi-Server Architectures

dotCMS ArchitecturesPush Publishing (shared nothing)

Multi-Server Architectures

Enabling Technologies

Geographic Load Balancing

• DNS-based

• Network-based

• Latency vs. Geography

Multi-Server Architectures

Enabling Technologies

Content Distribution Networks (CDNs)

• Object-based (Push)

• Caching (Pull)

• Full vs Host Isolation

Multi-Server Architectures

Enabling Technologies

Content Distribution Networks (CDNs)

Multi-Server Architectures

dotCMS Clustering

• Single pane-of-glass

• Shared resources

• Low node-to-node latency

• Local topology

Multi-Server Architectures

dotCMS Clustering

Multi-Server Architectures

dotCMS Push Publishing

• Multiple panes-of-glass that converge

• Isolated resources

• Tolerates high node-to-node latency

• Remote topology

• Unidirectional content flow

• Frontend content submission requires care

Multi-Server Architectures

dotCMS Push Publishing

Multi-Server Architectures

dotCMS Push Publishing

Multi-Server Architectures

dotCMS Push Publishing