Have you thought the ways we can implement a website in AEM? I am going to discuss some of the approaches here. Do let me know your thoughts through the post comments area.
1) AEM - The traditional way:
Here AEM is used as a pure solution. All the content and data are fed into AEM. The pages are authored in AEM including the DAM assets. In this scenario, there is no integration of any type of application with AEM. Here rendering is done through AEM.
2) AEM - As Hybrid Approach:
This is the most common way. Here the pages, assets are fed into AEM through authoring. Integrations like data access, social integrations are handled through web service calls. In this scenario there is always an integration layer, which could be used for search, data base authentication etc. Here rendering is through AEM.
3) AEM - As web content Model
Not a common way of implementing projects in industry, but yet to analyse the abundant capabilities. Here AEM is used as a data storage layer. The data gets into AEM from various sources like DB, third party data etc. Once the data is available in AEM, it can be made available to other systems through a different user interface technology other than AEM provided. Here rendering is through different technology. AEM makes the data available in a generalised way(Either JSON or XML formats) to the front end here.
How do we make the AEM content to third party applications?
The usual way of making AEM content to third party application is through a web service layer. We can utilise the sling API's to invoke the specific component or page and create required custom format JSON and pass it to service layer.
AEM contents are page oriented. How do we make component level information?
Have you heard of content fragments? The latest AEM provide content fragments - makes the Content As A Service (CaaS) way of implementation. These are components like structure which are not bonded to a specific page. We can author a content data with its metadata. Content fragments can even be transformed to its language versions. Watch this place for more details.
1) AEM - The traditional way:
Here AEM is used as a pure solution. All the content and data are fed into AEM. The pages are authored in AEM including the DAM assets. In this scenario, there is no integration of any type of application with AEM. Here rendering is done through AEM.
2) AEM - As Hybrid Approach:
This is the most common way. Here the pages, assets are fed into AEM through authoring. Integrations like data access, social integrations are handled through web service calls. In this scenario there is always an integration layer, which could be used for search, data base authentication etc. Here rendering is through AEM.
3) AEM - As web content Model
Not a common way of implementing projects in industry, but yet to analyse the abundant capabilities. Here AEM is used as a data storage layer. The data gets into AEM from various sources like DB, third party data etc. Once the data is available in AEM, it can be made available to other systems through a different user interface technology other than AEM provided. Here rendering is through different technology. AEM makes the data available in a generalised way(Either JSON or XML formats) to the front end here.
How do we make the AEM content to third party applications?
The usual way of making AEM content to third party application is through a web service layer. We can utilise the sling API's to invoke the specific component or page and create required custom format JSON and pass it to service layer.
AEM contents are page oriented. How do we make component level information?
Have you heard of content fragments? The latest AEM provide content fragments - makes the Content As A Service (CaaS) way of implementation. These are components like structure which are not bonded to a specific page. We can author a content data with its metadata. Content fragments can even be transformed to its language versions. Watch this place for more details.
