+ All Categories
Home > Documents > A Modular Microservice Architecture for Multi-everything

A Modular Microservice Architecture for Multi-everything

Date post: 03-Jan-2017
Category:
Upload: trinhhanh
View: 218 times
Download: 2 times
Share this document with a friend
49
28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 1 A Modular Microservice Architecture for Multi-everything Content Management Sixth International Conference on Creative Content Technologies May 25 - 29, 2014 - Venice, Italy Dr. Hans-Werner Sehring, T-Systems Multimedia Solutions, 28 May 2014
Transcript
Page 1: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 1

A Modular Microservice Architecture for Multi-everything Content Management Sixth International Conference on Creative Content Technologies May 25 - 29, 2014 - Venice, Italy Dr. Hans-Werner Sehring, T-Systems Multimedia Solutions, 28 May 2014

Page 2: A Modular Microservice Architecture for Multi-everything

Outline.

§  Modern Content Management Requirements. §  Content Management Today. §  Extended Requirements of Modern Applications.

§  Microservices. §  Concept-oriented Content Management (CCM). §  CCM Microservices for Multi-everything Content Management. §  Summary and Outlook.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 2

Page 3: A Modular Microservice Architecture for Multi-everything

Telekom

T-Mobile

T-Systems delivers ICT solutions for major corporations and public-sector organizations worldwide.

T-Systems

The Telekom subsidiaries provide products and services for the fixed network, mobile communications, the Internet and IPTV in Europe.

Deutsche Telekom delivers one-stop services and solutions: for all customer communications needs – at home, on the move and at work.

T-Mobile offers cell-phone solutions in the Netherlands, Austria, the Czech Republic, and the USA.

Deutsche Telekom. Partner for connected life and work.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 3

Page 4: A Modular Microservice Architecture for Multi-everything

*Internet agency ranking of Germany's Bundesverband Digitale Wirtschaft (BVDW).

T-Systems Multimedia Solutions.

§  1250 employees. §  9 offices. §  €122 mio. revenues. §  18 years of experience.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 4

Page 5: A Modular Microservice Architecture for Multi-everything

T-Systems Multimedia Solutions. Our Portfolio.

03.04.2014 – Vertraulich – Insight@MMS 5

CONSULTING Digital Communication Communication Strategies on digital Channels, Social Media Content Life Cycle Management Online Marketing and Monitoring

CONCEPT User Experience Content and Information Architecture Usability-Testing and Monitoring Prototypes

DESIGN Creation and Design Human-Machine-Interface. Digital Interface Corporate Design Transfer into Digital Interfaces Prototypes

TECH Development and Implementation Systems (CMS) and Technologies Consulting and Support Application Management and Operations

Cross Channel Commerce

Test & Integration Center

Cloud Application

Management Web Application Management

& Hosting

Mobile Solutions Cyber Security & Data Privacy

Social Intranet

Business Intelligence &

Big Data

Internet Relaunch

Procurement Excellence

eHR Solutions Maintenance 4.0

Contracting Commerce

Industry Commerce

Customer Service Solutions

Enterprise Process Portals

Page 6: A Modular Microservice Architecture for Multi-everything

MODERN CONTENT MANAGEMENT REQUIREMENTS.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 6

Page 7: A Modular Microservice Architecture for Multi-everything

Modern Content Management Requirements.

§  CMS today: foundation of web sites. §  media-agnostic content management. §  processes, internal and across system boundaries. §  editing, tools, and workflows, rights and roles. §  publication, rendering, and playout. §  systems integration.

§  Extended requirements of modern applications. §  marketing. §  sales. §  support, knowledge management. §  extranet: closed user groups, SSO, ... §  intranet: SSO, self service, ...

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 7

Page 8: A Modular Microservice Architecture for Multi-everything

CONTENT MANAGEMENT HEUTE. Content Management Today.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 8

Page 9: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 9

Content Management Today. Technical View on Content.

§  Initial idea of content management: in documents separate §  content, §  structure, and §  layout

1 Introduction

1.1 Def. of Content

Content is something miraculous.

Let’s structure it.

bold

spacing=...

section

subsection

paragraph paragraph

Introduction

Def. of content

Let‘s structure it.

Content is something miraculus.

Content consists of: data: media-agnostic, used for document production.

CI/CD, Device Info, ...

Page 10: A Modular Microservice Architecture for Multi-everything

Content Management Today. Web Content.

§  Further aspects of content modeling are relevant for web-based content dissemination: §  Navigation (for primary navigation, breadcrumbs, sitemap, ...). §  Variants of content.

§  language variants. §  full and short versions for full view, teaser, mobile site, ...

§  Multimedia documents, eventually in variants (e.g., print, online and preview). §  Editorial parameters, e.g. for directed search (“searchandizing”).

§  For documents, mobile apps, mobile sites, etc. similar aspects have to be taken into consideration.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 10

Page 11: A Modular Microservice Architecture for Multi-everything

ERWEITERTE ANFORDERUNGEN AUS MODERNEN ANWENDUNGEN.

Extended Requirements of Modern Applications.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 11

Page 12: A Modular Microservice Architecture for Multi-everything

Erweiterte Anforderungen aus modernen Anwendungen. „Website Evolution“.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 12

Copyright Ektron Inc. 2010

3From Content to Context to EngagementThe Future of Web Content Management is Context

+1.877.4.WEB.CMS

using. “Delighting customers doesn’t build loyalty,” note the authors of a recent Harvard Business Review article. “Reducing their effort—the work they must do to get their problem solved—does.”2 Showing an understanding for the customer and respecting the manner they want to do business breeds loyalty.

A Short History of the Corporate Website

The British engineer Sir Tim Berners-Lee invented the World Wide Web in 1989 during his time at CERN. Dr. Berners-Lee pioneered technologies that formed the backbone of the World Wide Web including HTTP, HTML, and the fi rst web browser. The fi rst website was deployed at CERN in 1991, providing technical specifi cations and guidelines for HTTP, HTML, and hypertext. In those early days, the Web was mostly limited to research and academia. The Web’s full business potential began to be realized with the advent of the graphical browser. In December 1994, a small startup called Netscape Communications released the fi rst version of its Netscape Navigator browser. By its very nature Navigator demonstrated the massive potential of the Web, and as a result drove corporations to quickly start moving their businesses to the Internet.

There have been four infl ection points marking the history of the corporate website:

1. Informational

2. Transactional

3. Persuasive

4. Contextual

The evolution of the corporate website

2 Stop Trying to Delight Your Customers” Dixon, Freeman and Toman, Harvard Business Review July/August 2010.

Transactional

Persuasive

Contextual

The evolution of the corporate website

‘95 – ’99

2000

2007

2011+

Transactional � IT-driven � Commerce. Portals. Personalization.

Informational � Brochure-ware Sites �Webmaster bottleneck

Persuasive �Marketing-driven � Focus on business outcomes

Contextual � Social � Personal

�Mobile � Interactive

[ektron, From Content to Context to Engagement , Whitepaper]

Page 13: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Domain Requirements.

§  Targeting, marketing automation: §  Adaption of presentation in order to make content accessible more easily:

content representation, page layout, search results, ... §  Optimization of content selection and presentation in order to make system fun to use

by offering optimal user experience. §  Leading the users to specific content (and finally to conversion).

§  Multi-site management: §  Landing pages, microsites, campaigns. §  Reusing content, software, and web components, optimize operations.

§  Cross-channel marketing: §  Shifting focus from Point of Sale (PoS) to Point(s) of Contact in order to attract users. §  Iteratively measuring success and improving a site w.r.t. specific goals. §  Learn about user journeys.

–öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 28.05.2014 13

Page 14: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Software System Requirements.

§  Technical answer to the domain requirements: multi-everything. §  Multimedia. §  Multilingualism. §  Multi-site / Multi-brand Systems: Multi-tenancy. §  Multi-device. §  Multi-channel, Cross-channel. §  Personalization, Targeting.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 14

Page 15: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multimedia.

§  Studied well in the document world. §  Multimedia models, languages, etc. §  Sometimes disassembled into monomedia artifacts in CMSs to account for:

§  different sources for artifacts: video from streaming service, time codes from CMS, comments from social media, …

§  multi-language (e.g., different audio tracks for movie) §  multi-device (e.g., different video encodings of movie) §  personalization (e.g., subtitles to video)

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 15

Page 16: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multilingualism.

§  “Same” content in different language, locales, etc. §  Typical pattern:

§  master copy in default language §  localized variants referring to it §  with localized variant fall back to default language §  not only content; also, e.g., layout: RTL languages etc.

§  Open: translation process §  actuality §  localization of prices, availability, legal constraints, …

=> multiple departments involved §  Open: variants of multimedia artifacts (image, video, …)

§  are they localized? §  all artifacts, or only some?

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 16

Page 17: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multilingualism Example.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 17

Page 18: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multi-site / Multi-brand Systems.

§  For different reasons there are content management platforms hosting more than on site: §  multi-site: the main web site, a corporate web site, microsites, … §  multi-brand: present a family of products

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 18

Page 19: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multi-tenancy.

§  Technically, Multi-site / Multi-brand Systems are forms of multi-tenancy. These tasks are accomplished by multi-tenant content management systems.

§  Different from multi-tenancy as in, e.g., databases, where applications are isolated from each other.

§  Options: §  Shared content (e.g., products) / protected content (e.g., financial figures). §  Shared functionality (e.g., search) / specific functionality (e.g., order forms). §  Shared data (e.g., global search) / specific data (e.g., site-specific search). §  Central editorial board / distributed editors.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 19

Page 20: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multi-device.

§  Web sites are offered in a form that does not only ensure correct display on the various stationary browsers, but also on mobile devices.

§  Above warranting the correct display some sites demand for device-optimized mobile variants, e.g.: §  using the device OS’s native look and feel §  using specific hardware features

§  Alternatives: §  native Apps §  responsive design

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 20

Page 21: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Multi-channel.

§  Same content is published on different media. §  Pull publication: web, mobile, API, SEO information, tracking, … §  Push publication: social media, newsletter, … §  Next step: cross-channel, have connected channels, track user journeys.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 21

Site Mobile Site RESTful API robots.txt Facebook Twitter Newsletter

Page 22: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Personalization.

§  The goal of targeting / marketing automation is primarily reached by means of personalization with the goal of contextualizing content presentation.

§  Determine which content and in what presentation is most appealing (helpful…) the user in the current usage context.

§  „Content is king“ è „Context is king“

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 22

1From Content to Context to EngagementThe Future of Web Content Management is Context

+1.877.4.WEB.CMS

About This White Paper

This document is intended for senior executives who want to understand the changing nature of web content management.

The web has become mission-critical for business, with websites the most important channel for sales, marketing, and customer support. As websites have evolved, visitor expectations for those sites have also changed. From a web perspective, visitor context is the key to providing experiences that deliver business results.

Web content management must expand their capabilities to align the content a website delivers against the context of its online visitors – why they are visiting any site, how they’re visiting, where they’ve come from, what content they’re consuming and who they are – all factors making up the visitor’s online web persona.

Context shortens sales cycles, produces higher quality leads, and grows revenue. Context increases customer engagement and loyalty.

A “content management system” is no longer enough to successfully attract and retain your audience. Managing content will no longer be enough.

Content + context will drive successful engagement

This document explores Ektron’s vision of the future of web content management, and how successful businesses will use visitor context to deliver relevant content to their online audiences.

.

A “content management system” is no

longer enough...”

[ektron, From Content to Context to Engagement , Whitepaper]

Page 23: A Modular Microservice Architecture for Multi-everything

Extended Requirements of Modern Applications. Targeting.

§  In field of content management: Web Content Management (WCM) now named §  Web Experience Management (WEM) §  Customer Experience Management (CEM, CXM)

§  Currently of particular interest:, personalization, marketing automation, or similar.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 23

Tailored page

Feedback

Rework and/or rules

Conversion Semi-automatic product approaches: §  Marketing Automation (Adobe) §  Create/Deliver/Optimize (eZ Systems) §  Adaptive Personalization (CoreMedia).

Page 24: A Modular Microservice Architecture for Multi-everything

MICROSERVICES.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 24

Page 25: A Modular Microservice Architecture for Multi-everything

Microservices. One First Definition.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 25

In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. [http://martinfowler.com/articles/microservices.html]

Page 26: A Modular Microservice Architecture for Multi-everything

Microservices. Common Characteristics.

§  Not a new approach, can be seen in many places. Currently consolidation of experiences and identifying common characteristics.

§  Goals: §  no SW monoliths in the sense of statically linked software modules (e.g., layered

architecture), but components with independent lifecycles §  service-oriented approach,

structure software (and teams) according to business capabilities, not functionalities §  support “agile architecture”, design for evolution

§  Uniform API (“published interface”), required for orthogonal composition of system building blocks.

§  P&F style communication with “smart filters, dumb pipes”: encapsulated logic, simple protocols.

§  No shared knowledge; e.g., local storage instead of centralized databases => no common database schema, no commonly agreed-upon conceptual models.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 26

Page 27: A Modular Microservice Architecture for Multi-everything

CONCEPT-ORIENTED CONTENT MANAGEMENT.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 27

Page 28: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). Requirements for Personalizable Systems.

§  Requirements: §  Users want to adapt (personalize) content to their current working context individually,

while §  existing content is preserved and §  cooperation between users is maintained.

§  Demand: open and dynamic environments §  Openness: models …

§  are not limited to predefined concepts and §  can be changed at any time.

§  Dynamics: content management systems … §  follow model change without interrupting the domain experts’ work and §  maintain existing contents and communication structures.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 28

Page 29: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). Orthogonal Personalization.

§  Content personalization: §  content, concepts,

schema, context. §  includes

presentation personalization. §  Structure personalization:

§  Schema (attributes, relationships, constraints). §  Categories (create new, recategorize).

§  Implemented through openness and dynamics.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 29

system-wide content

group content

personal content

personalize

integrate

personalize

integrate

Page 30: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). Contributions.

§  The key requirements of openness and dynamics are met by the Concept-oriented Content Management (CCM) approach by means of its key contributions: §  Modeling language

§  Modeling performed by domain expert. §  Open for changes.

§  Model-driven system development §  Incremental generation. §  Fully automatic,

without developer intervention. §  Software architecture

§  Component-based. §  Evolution friendly.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 30

model Historiography from Time import Timestamp from Topology import Place class Professor { content image concept characteristic n :String relationship publs :Work* }

Intermediate model

… … … …

a:AssetClass b:AssetClass

m:Model superClass

h

Political_Iconography (PI)

Artists Regents

m client1

m client m med2

DB

m client2

DB

m med1

m distrib1 m distrib2

DB

Page 31: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). Logical CCM Architecture: Components

§  CCMSs consist of components §  one component for each domain model §  cooperation for domain combinations §  integration to model revisions and to derive variants

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 31

orga

niza

tion

stru

ctur

e

application structure

c c

c c1 c c2

c b1 c b0 c b2

c d1

c d11 c d12

c d2

c d21

c d0

c a integration

cooperation

component c i

Page 32: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). CCMS Implementation: Modules

§  Modules implement components §  Reconfigurability at runtime

for dynamics through: §  Separation of Concerns

by module kinds with distinguished functionality,

§  uniform module API, and §  statelessness of modules.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 32

m 1a m 1b m 11 m 12

m 1a m 1b

m 21

application structure

m 1a m 1b

m 11 m 12

m 1 m 0 m 1

m 1 c c

c c1 c c2

c b0 c b1

m 2a m 2

c b2 c a

m 11 m 12 c d11 c d12 c d21

m 0 m 1 c d0

m 2a m 2

c d2 c d1

implemen- tation

integration cooperation component k i communication implementation module m i

orga

niza

tion

stru

ctur

e

Page 33: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). Module kinds for CCMSs

§  Module kinds for the construction of CCMSs: §  Client module:

Mapping to the generic concepts of a base system §  Server module:

Provision of functionality according to a standardized interface §  Coordination module:

Delegation of requests according to a certain strategy §  Adaptation module:

Conversion between different models §  Distribution module:

Connection to remove module of a (distributed) component

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 33

Page 34: A Modular Microservice Architecture for Multi-everything

Concept-oriented Content Management (CCM). A Microservices View

§  CCMSs follows a microservices approach. §  It exhibits the agreed-upon properties of microservices:

§  Components encapsulating business capabilities §  Architecture made for evolution §  Separation of Concerns in implementations (modules) §  Uniform published interface and decentralized internal schemas

<-> CCMSs’ component (server module) and internal module interfaces §  CCM’s additions:

§  Caring about components’ microarchitecture in order to allow dynamic evolution. §  Making remote access explicit through distribution and server modules.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 34

Page 35: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 35

CCMS Architecture as a Microservices. Modules as Filters.

§  Module interface: API generated from the content model.

module 1

response of module 1 request to module 1

response of base module request to base module

Page 36: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 36

CCMS Architecture as a Microservices. Modules Combinations as Filter Chains.

§  Module combinations: The generated API with pre-defined functionality allows to combine modules freely. They are arranged in a layered architecture, where the access pattern resembles pipes and filters (pull chain).

module 1

module 2 module 1 uses module 2

module 3

module 4 module 5

module 2 uses module 3

module 3 uses module 4 and/or module 5

response of module 1 (content) (pull) request to module 1

content flow

Page 37: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 37

CCMS Architecture as a Microservices. Distribution Modules as Pipes for Remote Calls.

§  Distribution: explicit through module combinations incorporating distribution modules. Other module combinations use implementation language bindings (direct calls).

module 1 at site 1

distribution module

distribution module

module 2 at site 2

module 1

module 2

(module 1 uses module 2)

(module 1 uses module 2 remotely)

Page 38: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 38

CCMS Architecture as a Microservices. Uniform component API.

§  Component API: Component APIs are defined by server modules according to some standard interface, e.g., as a RESTful service.

component

module 1

module 2

server module

response of component request to component

Page 39: A Modular Microservice Architecture for Multi-everything

CCM MICROSERVICES FOR MULTI-EVERYTHING CONTENT MANAGEMENT.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 39

Page 40: A Modular Microservice Architecture for Multi-everything

CCM Microservices for Multi-everything Content Management.

§  The demands for §  Multimedia §  Multilingualism §  Multi-tenancy: Multi-site / Multi-brand Systems §  Multi-device §  Multi-channel, Cross-channel §  Personalization, Targeting

can be addressed by a CCMS with the usual means.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 40

Page 41: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 41

CCM Microservices for Multi-everything Content Management. Multimedia.

§  Media can be stored in different asset management repositories, remote locations, … §  A coordination module combines content into aggregated assets. §  If the content structures differ, adaptation modules unify the structures.

Example: pictures without timing information are related to sound (with timeline). §  Then, multimedia presentations can be created. Ex.: Timing can be added to the pictures.

server module: multimedia

coordination module: media combination

adaption module: media 1 adaptation module: media 2

client module: media 1 client module: media 2

coordination module: multimedia assembly

client module: multimedia scripts

Page 42: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 42

CCM Microservices for Multi-everything Content Management. Multilingualism.

§  Content for different languages is hosted in different repositories, accessible through client modules.

§  Adaption modules change the schema, so that language variants of content refer to one “master content” in the default language.

§  A coordination module selects content from one of the base modules according to a chosen language. Language variants are related to the “master content”.

server module: multi-language

coordination module: language selection

adaptation module: en adaptation module: de adaptation module: it

client module: en client module: de client module: it

Page 43: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 43

CCM Microservices for Multi-everything Content Management. Multi-tenancy.

§  Content is accessed by one or more client modules. §  Content is delivered by one server module per tenant. §  One coordination module (or multiple) provides the corresponding view on the content. §  Eventually one adaptation module per tenant establishes the schema required by its tenant.

server module: tenant 1

coordination module: whole content

adaptation module en

client module: content 1 client module: content 2

server module: tenant 2 server module: tenant 3

adaptation module: tenant 1 adaptation module: tenant 2 adaptation module en adaptation module: tenant 3

Page 44: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 44

CCM Microservices for Multi-everything Content Management. Multi-device, Multi-channel.

§  Content is delivered by one server module per device/channel. §  One coordination module per device/channel augments the main content with device-/

channel-specific variants (e.g., shorter/longer texts, smaller/larger images, navigation, …). §  Adaptation modules establish the schema required for that augmentation.

server module: device 1

coordination module: device 1

client module: content

client module: device 1 specific content

adaptation module:device 1

server module: device 2

coordination module: device 2

adaptation module:device 2 client module: device 2 specific content

Page 45: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 45

CCM Microservices for Multi-everything Content Management. Personalization.

§  Personalization according to the basic personalization pattern of CCMSs. §  Additionally, a server module to access plain content for the non-personalized case can be

added. §  Alternatively, there can be one single server module, and a subordinate coordination

module decides whether to show plain content or that for a specific target group.

server module: personalized content

coordination module: personalization

adaptation module

client module 1: plain content

client module 2: personalized content

server module: plain content

Page 46: A Modular Microservice Architecture for Multi-everything

SUMMARY AND OUTLOOK.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 46

Page 47: A Modular Microservice Architecture for Multi-everything

Summary.

§  Basic content management is well established for content creation and delivery. §  Additional requirements are emerging from application domains, especially marketing and

sales, as well as knowledge representation. §  Content management systems are no longer isolated solutions.

§  The technical answers to domain requirements are similar: multi-everything. All deal with §  variance of representations and §  adaptations of content.

§  Concept-oriented content management is an approach that fits well into modern software engineering approaches – adaptable, non-monolithic, open, dynamic, …

§  By its nature it allows to compose components for contemporary requirements.

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 47

Page 48: A Modular Microservice Architecture for Multi-everything

Outlook.

§  So far CCMSs have only been applied in scientific contexts, not for commercial projects (customers). Such applications are yet to come.

§  It might be interesting to look into pattern library for CCMS configurations that maps requirements to typical module constellations. This should be interesting not only for CCMSs, but for CMSs in general.

§  This way some of the multi-* features should be unified. At least the ability to compose multi-* features should be further examined and manifested in patterns.

§  One future research direction will be more support for marketing automation: §  Feedback: tracking etc. can be applied for A/B testing, personalization, detection of

conversion blockers, … §  User journeys exceeding the CCMS should be tracked to make use of that knowledge. §  CCMS evolution might be enhanced if conversions can be detected. Eventually they

should automatically adapt on that occasion (task completed, context should change).

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 48

Page 49: A Modular Microservice Architecture for Multi-everything

28.05.2014 –öffentlich– Dr. H.-W. Sehring / A Modular Microservice Architecture for Multi-everything Content Management 49

Thank you for your attention!

Dr. Hans-Werner Sehring Principal Software Architect

T-Systems Multimedia Solutions GmbH Binderstraße 26, 20146 Hamburg, Germany Phone +49 (40) 570062 8049 E-mail [email protected]

Address Contacts

http://www.linkedin.com/in/hwsehring

https://www.xing.com/profile/HansWerner_Sehring


Recommended