A new approach to get a CMS for the digital transformation

1. com
NoCMS
… from monolithic CMS to dissolved CMS

2. com
SPEAKER
PHILIPP BÄRFUSS
2005-2016 CTO @Magnolia
developer, architect
product manager
organisation coach
@pbaerfuss! "# woowai.com/pb woowai.com/pb

3. com
DO YOU BUILD A NEW CMS?
SPEAKER
I am not a masochist!

4. com
BUT I LIKE TO SHARE MY PROBLEM AND IDEAS
SPEAKER
… and hope some will implement it ;-)

5. the liberating company
.com

6. com
BETTER PRODUCTS - BETTER ORGANISATIONS
COMPANY
PRODUCT MANAGEMENT
Ship 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


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

8. com
CHALENGE
WHAT IS A CMS?
Delivery
Storage
Authoring
DELIVERY
(
AUTHORING
)
STORAGE

+

9. com
CONTENT DRIVEN VS FUNCTIONAL
CHALLENGE
Functional
Content
Digital Transformation
0
25
50
75
100
Brochure Site Digital Business
Functional
Content

10. com
MICROSERVICE ARCHITECTURE
MICROSERVICES
Cloud solutions are installed once and need to scale

11. +
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 Fowler
http://martinfowler.com/articles/microservices.html

12. +
com
These services are built around business capabilities and
independently deployable by fully automated
deployment machinery.
MICROSERVICES
– Martin Fowler
http://martinfowler.com/articles/microservices.html
,

13. +
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 Fowler
http://martinfowler.com/articles/microservices.html

14. +
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 Fowler
http://martinfowler.com/articles/microservices.html
-

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

16. com
MICROSERVICES
Traditional SOA Microservices
Messaging 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 systems
Lines of code per service Hundreds or thousands of lines of code 100 or fewer lines of code
State Stateful Stateless
Messaging type Synchronous: wait to connect Asynchronous: publish and subscribe
Databases Large relational databases NoSQL or micro-SQL databases blended
with conventional databases
Code type Procedural Functional
Means of evolution Each big service evolves Each small service is immutable and can
be abandoned or ignored
Means of systemic change Modify the monolith Create a new service
Means of scaling Optimize the monolith Add more powerful services and cluster
by activity
System-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

17. +
com
– Nic Ferrier
“a microservice should be re-
writeable in about 2 weeks”
MICROSERVICES

18. com
MONOLITHIC CMS
CHALLENGE
I don’t want to integrate my platform into a CMS

19. com
MONOLITHIC
NOCMS
STORAGE

AUTHORING
)
DELIVERY
(

20. com
HEADLESS CMS
CHALLENGE
Disconnects authoring, leaves me on my own for the
delivery task and generates a content silo.

21. com
HEADLESS
NOCMS
STORAGE

AUTHORING
)
DELIVERY
(

22. com
NOCMS
NOCMS
.. a catchy term for a new proposal

23. com
DISOLVED CMS
NOCMS
a CMS for the digital transformation

24. com
NOCMS
CONTENT NODES

CONTEXT
♥
AGGREGATOR
/ AUTHORING
)
PRODUCERS
%
0
0

ROUTER
(
%

25. com
NOCMS
CONTENT NODES

CONTEXT
♥
AGGREGATOR
/ AUTHORING
)
PRODUCERS
%
0
0

ROUTER
(
SEARCH
1
CACHE
2
SECURITY
3

26. com
INTEGRATION
NOCMS
How to add other stuff.

27. com
MONOLITHIC
NOCMS
STORAGE

AUTHORING
)
DELIVERY
(
MOBILE API
4
TRANSLATION
4
SHOP
45
5
5

28. com
HEADLESS
NOCMS
STORAGE

CLIENT
6
AUTHORING
)
MOBILE API
4
TRANSLATION
4
SHOP
4
5
5
5
PRODUCERS
%
STORAGE

DELIVERY
(

29. com
DISSOLVED
NOCMS
CONTENT NODES

CONTEXT
♥ AGGREGATOR
/ AUTHORING
)
PRODUCERS
%
ROUTER
(
MOBILE API
4 TRANSLATION
4
SHOP
4

30. com
INTEGRATION
Dissolved + United
NOCMS
Monolithic + Integrations
vs

31. com
VALUE PROPOSITION
continuously deploy changes
no limits in scaling
all peaces replaceable
universal experience for authors
NOCMS

32. com
CUSTOMER
functional sites
digital business
skilled IT departments
NOCMS

33. com
BUILD ALL THAT FROM SCRATCH?
AWS
AWS has a surprisingly well fitting palette of services

34. com
AWS
JUMP START
rich set of services
scales
well known

35. com
AWS
7
7 7
77

36. com
AWS
7
7
7

37. com
CMS AS AN API
API
what we need are contracts

38. com
CONTENT
API
… lets try to catch that content bus

39. com
EVENTS
CONTENT
 ?
subscribe
notify
get(id, context)
push(content)
?
Web Hooks

40. com
CONTENT FLOWS
CONTENT



Local Store
Headquarter
Stage
Europe

Live


41. com
CONTENT FLOW
CONTENT


2
Content
Queue
Cache
TRANSLATION
4

42. com
DELIVERY
API
lets play together!

43. com
DELIVERY
CONTENT NODES

CONTEXT
♥
ROUTER
(
PRODUCERS
%
0
AGGREGATOR
/

44. com
CONTEXT
user/groups/roles
languages
device
…
DELIVERY

45. com
DELIVERY
PRODUCER
%
PRODUCER
%
PRODUCER
%
produce (content, channel)
AGGREGATOR
/
SHOP
4

46. com
LAMBDA
AWS
The dust of life. Finally a content bus.

47. com
AWS LAMBDA

48. com
AWS LAMBDA

49. com
AWS LAMBDA

50. com
WHAT IS MISSING?
AUTHORING
No solution for the authoring

51. com
STRUCTURED AND IN CONTEXT
AUTHORING
… unified authoring experience wanted

52. com
AUTHORING
CONTENT NODE

AUTHORING
)
CONTENT NODE

CONTENT NODE


53. com
AUTHORING
CONTENT NODE

AUTHORING
)
Data Model
push

54. com
AUTHORING
6
AUTHORING
)
author.js
FORM
8
delegate
APPLICATION
?
IN CONTEXT
9

55. com
AUTHORING
6
AUTHORING
)
PAGE
8 PRODUCER
%annotates
edit(id)
FORM
8 CONTENT NODE
Meta Model

56. com
NEXT?
API
some of the API could be tested with a basic Node.js
implementation

57. com
LET’S SUM IT UP
CONCLUSION
… so what have we learned

58. com
CONCLUSION
Digital Transformation

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

60. com
CONCLUSION
:
@pbaerfuss
@woowai_com
!
!
∠woowai.com/pb
! #nocms