By Jonathan Bordoli – A cloud content services approach distributes core functions of the CMS to separate microservices units for use by modules of an integrated stack or independent applications using common APIs. Those units might include content tagging services, device-specific content rendering services or information rights management services governing who can see what content.

Microservices are the natural evolution of a reductionist approach to computer programming. Early programs, and hence applications, were monolithic — built as large single units. As programming languages evolved, so did the idea of breaking the programs up in to smaller pieces, using capabilities known as subroutines and functions. These subroutines and functions could physically exist in different program files, each having its own development lifecycle.

Cloud microservices models take those subroutines and spin them off independently so that capabilities of applications are broken into small units and distributed throughout the computing resources of the cloud. These units provide specific functionality and cooperate through message passing.
Cloud microservices models take those subroutines and spin them off independently so that capabilities of applications are broken into small units and distributed throughout the computing resources of the cloud. These units provide specific functionality and cooperate through message passing. Read more: