Technical Q&A: Architecture, Part 1: Felix Meschberger, Stephane Moreau, Alexander Morin
Technical Q&A: Architecture, Part 1: Felix Meschberger, Stephane Moreau, Alexander Morin
Technical Q&A: Architecture, Part 1: Felix Meschberger, Stephane Moreau, Alexander Morin
Terminology
Deployments
Technical Topics
Tracking
Image Serving & Spare Servers
DNS Masks and Load Balancing
Term Description
Container A physical or virtual server or a container in a light-weight virtualization environment
such as OpenVZ
Service A function implemented by Campaign executed as a process (or group of processes)
on a single Container
Instance A collection of Services together providing some functionality of Adobe Campaign.
An instance may span multiple Containers for failover or scalability. Each Container
in a single Instance is typically configured the same.
Deployment A method of installing Adobe Campaign to on one or more Containers with multiple
Services.
Platform Aspects
One Binary to rule them All
Database Centric
Other Inter-Process Communication
SOAP
UDP
File System
Shared Memory
Configuration Files
serverConf.xml – global, shared
config-<instance>.xml – per instance configuration
Standalone
Standard
Enterprise
Mid-sourcing
Power Booster/Power Cluster
Special Case
Development
Small Scale
Entry Level
Simple
Server Failover
Load Balancing
Improved Performance
Typical Use Today
Enhanced Security
Protect DB
Improved Stability
Better SLA Handling
Separation of Concerns
DB remains On Premise
Delegation of SLA
Delegation of IP and
Bandwidth Management
High Volume
Extension of Mid-
sourcing Deployment
Added Performance
Added Resilience
High Volume
Message Center
Interaction
Tracking
Image Serving & Spare Servers
DNS Masks and Load Balancing