nocms - from monolithic cms to dissolved cms

60
com NoCMS … from monolithic CMS to dissolved CMS

Upload: philipp-baerfuss

Post on 21-Jan-2017

595 views

Category:

Software


4 download

TRANSCRIPT

Page 1: NoCMS - from monolithic CMS to dissolved CMS

com

NoCMS… from monolithic CMS to dissolved CMS

Page 2: NoCMS - from monolithic CMS to dissolved CMS

com

SPEAKER

PHILIPP BÄRFUSS

2005-2016 CTO @Magnolia developer, architect product manager organisation coach

@pbaerfuss! "# woowai.com/pb woowai.com/pb

Page 3: NoCMS - from monolithic CMS to dissolved CMS

com

DO YOU BUILD A NEW CMS?SPEAKER

I am not a masochist!

Page 4: NoCMS - from monolithic CMS to dissolved CMS

com

BUT I LIKE TO SHARE MY PROBLEM AND IDEAS

SPEAKER

… and hope some will implement it ;-)

Page 5: NoCMS - from monolithic CMS to dissolved CMS

the liberating company

.com

Page 6: NoCMS - from monolithic CMS to dissolved CMS

com

BETTER PRODUCTS - BETTER ORGANISATIONS

COMPANY

PRODUCT MANAGEMENTShip value not products.

Everything is a product and so product management

methodologies like value proposition design are key for the success of all kinds of initiatives.

◎PLATFORM AND

IMPLEMENTATION

In the world of software products and online services we want to be the backbone of highly valuable

solutions.

%ORGANISATION COACHING

Coaching of startups and SMEs for liberating and agile structures.

Agile and creative working and collaboration methodologies

Page 7: NoCMS - from monolithic CMS to dissolved CMS

com

CHALLENGE

IMPLEMENTATION AND PLATFORM

In the world of software products and online services we want to be the backbone of highly valuable

solutions.

' A/B Testing

Help Texts

Profile

Subscription Plans

UI

Page 8: NoCMS - from monolithic CMS to dissolved CMS

com

CHALENGE

WHAT IS A CMS?

Delivery

Storage

Authoring

DELIVERY

(

AUTHORING

)STORAGE

+

Page 9: NoCMS - from monolithic CMS to dissolved CMS

com

CONTENT DRIVEN VS FUNCTIONAL

CHALLENGE

Functional

Content

Digital Transformation

0

25

50

75

100

Brochure Site Digital Business

Functional

Content

Page 10: NoCMS - from monolithic CMS to dissolved CMS

com

MICROSERVICE ARCHITECTUREMICROSERVICES

Cloud solutions are installed once and need to scale

Page 11: NoCMS - from monolithic CMS to dissolved CMS

+

com

“In short, the microservice architectural style [1] 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.

MICROSERVICES

– Martin Fowlerhttp://martinfowler.com/articles/microservices.html

Page 12: NoCMS - from monolithic CMS to dissolved CMS

+

com

These services are built around business capabilities and independently deployable by fully automated deployment machinery.

MICROSERVICES

– Martin Fowlerhttp://martinfowler.com/articles/microservices.html

,

Page 13: NoCMS - from monolithic CMS to dissolved CMS

+

com

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.”

MICROSERVICES

– Martin Fowlerhttp://martinfowler.com/articles/microservices.html

Page 14: NoCMS - from monolithic CMS to dissolved CMS

+

com

Microservice practitioners, usually have come from an evolutionary design background and see service decomposition as a further tool to enable application developers to control changes in their application without slowing down change. Change control doesn't necessarily mean change reduction - with the right attitudes and tools you can make frequent, fast, and well-controlled changes to software.”

MICROSERVICES

– Martin Fowlerhttp://martinfowler.com/articles/microservices.html

-

Page 15: NoCMS - from monolithic CMS to dissolved CMS

com

MICROSERVICES

http://www.pwc.com/us/en/technology-forecast/2014/cloud-computing/features/microservices.html

Page 16: NoCMS - from monolithic CMS to dissolved CMS

com

MICROSERVICES

Traditional SOA MicroservicesMessaging type Smart, but dependency-laden ESB Dumb, fast messaging (as with Apache

Kafka)Programming style Imperative model Reactive actor programming model that

echoes agent-based systemsLines of code per service Hundreds or thousands of lines of code 100 or fewer lines of codeState Stateful StatelessMessaging type Synchronous: wait to connect Asynchronous: publish and subscribeDatabases Large relational databases NoSQL or micro-SQL databases blended

with conventional databasesCode type Procedural FunctionalMeans of evolution Each big service evolves Each small service is immutable and can

be abandoned or ignoredMeans of systemic change Modify the monolith Create a new serviceMeans of scaling Optimize the monolith Add more powerful services and cluster

by activitySystem-level awareness Less aware and event driven More aware and event driven

http://www.pwc.com/us/en/technology-forecast/2014/cloud-computing/features/microservices.html

Page 17: NoCMS - from monolithic CMS to dissolved CMS

+

com

– Nic Ferrier

“a microservice should be re-writeable in about 2 weeks”

MICROSERVICES

Page 18: NoCMS - from monolithic CMS to dissolved CMS

com

MONOLITHIC CMSCHALLENGE

I don’t want to integrate my platform into a CMS

Page 19: NoCMS - from monolithic CMS to dissolved CMS

com

MONOLITHICNOCMS

STORAGE

AUTHORING

)

DELIVERY

(

Page 20: NoCMS - from monolithic CMS to dissolved CMS

com

HEADLESS CMSCHALLENGE

Disconnects authoring, leaves me on my own for the delivery task and generates a content silo.

Page 21: NoCMS - from monolithic CMS to dissolved CMS

com

HEADLESSNOCMS

STORAGE

AUTHORING

)

DELIVERY

(

Page 22: NoCMS - from monolithic CMS to dissolved CMS

com

NOCMSNOCMS

.. a catchy term for a new proposal

Page 23: NoCMS - from monolithic CMS to dissolved CMS

com

DISOLVED CMSNOCMS

a CMS for the digital transformation

Page 24: NoCMS - from monolithic CMS to dissolved CMS

com

NOCMS

CONTENT NODES

CONTEXT

♥AGGREGATOR

/ AUTHORING

)

PRODUCERS

%

0

0

ROUTER

(

%

Page 25: NoCMS - from monolithic CMS to dissolved CMS

com

NOCMS

CONTENT NODES

CONTEXT

♥AGGREGATOR

/ AUTHORING

)

PRODUCERS

%

0

0

ROUTER

(

SEARCH

1CACHE

2

SECURITY3

Page 26: NoCMS - from monolithic CMS to dissolved CMS

com

INTEGRATIONNOCMS

How to add other stuff.

Page 27: NoCMS - from monolithic CMS to dissolved CMS

com

MONOLITHICNOCMS

STORAGE

AUTHORING

)

DELIVERY

(

MOBILE API

4

TRANSLATION

4

SHOP

45

5

5

Page 28: NoCMS - from monolithic CMS to dissolved CMS

com

HEADLESSNOCMS

STORAGE

CLIENT

6

AUTHORING

)

MOBILE API

4

TRANSLATION

4

SHOP

45

5

5PRODUCERS

%

STORAGE

DELIVERY

(

Page 29: NoCMS - from monolithic CMS to dissolved CMS

com

DISSOLVEDNOCMS

CONTENT NODES

CONTEXT

♥ AGGREGATOR

/ AUTHORING

)

PRODUCERS

%

ROUTER

(

MOBILE API

4 TRANSLATION

4

SHOP

4

Page 30: NoCMS - from monolithic CMS to dissolved CMS

com

INTEGRATION

Dissolved + United

NOCMS

Monolithic + Integrations

vs

Page 31: NoCMS - from monolithic CMS to dissolved CMS

com

VALUE PROPOSITION

continuously deploy changes

no limits in scaling

all peaces replaceable

universal experience for authors

NOCMS

Page 32: NoCMS - from monolithic CMS to dissolved CMS

com

CUSTOMER

functional sites

digital business

skilled IT departments

NOCMS

Page 33: NoCMS - from monolithic CMS to dissolved CMS

com

BUILD ALL THAT FROM SCRATCH? AWS

AWS has a surprisingly well fitting palette of services

Page 34: NoCMS - from monolithic CMS to dissolved CMS

com

AWS

JUMP START

rich set of services

scales

well known

Page 35: NoCMS - from monolithic CMS to dissolved CMS

com

AWS

77 7

77

Page 36: NoCMS - from monolithic CMS to dissolved CMS

com

AWS

7

7

7

Page 37: NoCMS - from monolithic CMS to dissolved CMS

com

CMS AS AN APIAPI

what we need are contracts

Page 38: NoCMS - from monolithic CMS to dissolved CMS

com

CONTENTAPI

… lets try to catch that content bus

Page 39: NoCMS - from monolithic CMS to dissolved CMS

com

EVENTSCONTENT

?subscribe

notify

get(id, context)

push(content)

?Web Hooks

Page 40: NoCMS - from monolithic CMS to dissolved CMS

com

CONTENT FLOWSCONTENT

Local Store

Headquarter

Stage

Europe

Live

Page 41: NoCMS - from monolithic CMS to dissolved CMS

com

CONTENT FLOWCONTENT

2Content

Queue

Cache

TRANSLATION

4

Page 42: NoCMS - from monolithic CMS to dissolved CMS

com

DELIVERYAPI

lets play together!

Page 43: NoCMS - from monolithic CMS to dissolved CMS

com

DELIVERY

CONTENT NODES

CONTEXT

♥ROUTER

(

PRODUCERS

%

0

AGGREGATOR

/

Page 44: NoCMS - from monolithic CMS to dissolved CMS

com

CONTEXT

user/groups/roles

languages

device

DELIVERY

Page 45: NoCMS - from monolithic CMS to dissolved CMS

com

DELIVERY

PRODUCER%

PRODUCER%

PRODUCER%

produce (content, channel)

AGGREGATOR

/SHOP

4

Page 46: NoCMS - from monolithic CMS to dissolved CMS

com

LAMBDAAWS

The dust of life. Finally a content bus.

Page 47: NoCMS - from monolithic CMS to dissolved CMS

com

AWS LAMBDA

Page 48: NoCMS - from monolithic CMS to dissolved CMS

com

AWS LAMBDA

Page 49: NoCMS - from monolithic CMS to dissolved CMS

com

AWS LAMBDA

Page 50: NoCMS - from monolithic CMS to dissolved CMS

com

WHAT IS MISSING?AUTHORING

No solution for the authoring

Page 51: NoCMS - from monolithic CMS to dissolved CMS

com

STRUCTURED AND IN CONTEXTAUTHORING

… unified authoring experience wanted

Page 52: NoCMS - from monolithic CMS to dissolved CMS

com

AUTHORING

CONTENT NODE

AUTHORING

)

CONTENT NODE

CONTENT NODE

Page 53: NoCMS - from monolithic CMS to dissolved CMS

com

AUTHORING

CONTENT NODE

AUTHORING

)Data Model

push

Page 54: NoCMS - from monolithic CMS to dissolved CMS

com

AUTHORING

6AUTHORING

)author.js

FORM

8delegate

APPLICATION?

IN CONTEXT

9

Page 55: NoCMS - from monolithic CMS to dissolved CMS

com

AUTHORING

6

AUTHORING

)

PAGE

8PRODUCER%annotates

edit(id)

FORM

8 CONTENT NODE

Meta Model

Page 56: NoCMS - from monolithic CMS to dissolved CMS

com

NEXT?API

some of the API could be tested with a basic Node.js implementation

Page 57: NoCMS - from monolithic CMS to dissolved CMS

com

LET’S SUM IT UPCONCLUSION

… so what have we learned

Page 58: NoCMS - from monolithic CMS to dissolved CMS

com

CONCLUSION

Digital Transformation

Page 59: NoCMS - from monolithic CMS to dissolved CMS

com

INSIGHTS

Digital businesses demand for a new integrative CMS approach

Microservices architecture fits well

CONCLUSIONS

Frameworks like AWS are ready

Authoring is the challenge and the chance for the CMS industry

Page 60: NoCMS - from monolithic CMS to dissolved CMS

com

CONCLUSION

:@pbaerfuss

@woowai_com

!!

∠woowai.com/pb

! #nocms