Among the new features in SDL Web 8 there are the Content Delivery Microservices, namely:
These microservices make up the Content Interaction Services and they expose the existing Content Delivery in-process APIs as RESTful services. They provide the server-side component in a Services-Oriented Architecture and act as data layer between the the web client and the Content Delivery Storage Layer.
According to the SDL marketing, these microservices:
In technical words, these microservices are self-contained, self-running entities, embedding an Apache Tomcat instance, which are in fact Spring Boot packages designed to (according to Spring documentation) "get you up and running as quickly as possible" and to provide an "easy way to create stand-alone, production-grade Spring based Applications that you can 'just run'".
There is a clear change in direction towards services and simplification in Web 8. The installation steps for each of the microservices are almost trivial, all having just a couple of configuration files needed for modifications. They can be run as standalone applications by simply executing the provided scripts, or alternatively, they can be installed as Windows services. There will be no need to install Tomcat or another application server, although you still can, if you choose to.
From a caching perspective, the microservices use the usual in-memory object cache that relies on the Cache Channel Service notification to expire its dependency cache regions. Web 8 also provides a set of native REST client libraries for each of the microservices. Their cache is much simpler -- TTL based in-memory cache.
More about the specifics of microservices, installation guides and explanations, in later posts.
- Audience Manager
- Content Deployer
- Contextual Image Delivery
- Discovery Service
- Dynamic Content
- Dynamic Linking
- Profiling and Personalization
- Metadata Query
- Taxonomy
- User Generated Content
These microservices make up the Content Interaction Services and they expose the existing Content Delivery in-process APIs as RESTful services. They provide the server-side component in a Services-Oriented Architecture and act as data layer between the the web client and the Content Delivery Storage Layer.
According to the SDL marketing, these microservices:
- Simplify upgrades, thus offering shorter time to value
- Modernize architecture, offering better separation between the web application and Tridion APIs
- Offer more flexibility with less downtime and improved scalability
- Improve quality, being self-running, contained and having less dependencies
In technical words, these microservices are self-contained, self-running entities, embedding an Apache Tomcat instance, which are in fact Spring Boot packages designed to (according to Spring documentation) "get you up and running as quickly as possible" and to provide an "easy way to create stand-alone, production-grade Spring based Applications that you can 'just run'".
There is a clear change in direction towards services and simplification in Web 8. The installation steps for each of the microservices are almost trivial, all having just a couple of configuration files needed for modifications. They can be run as standalone applications by simply executing the provided scripts, or alternatively, they can be installed as Windows services. There will be no need to install Tomcat or another application server, although you still can, if you choose to.
From a caching perspective, the microservices use the usual in-memory object cache that relies on the Cache Channel Service notification to expire its dependency cache regions. Web 8 also provides a set of native REST client libraries for each of the microservices. Their cache is much simpler -- TTL based in-memory cache.
More about the specifics of microservices, installation guides and explanations, in later posts.
Comments