Liferay Topics for Revision

Use for creating DAO / POJOs / SQL scripts  based on  service.xml. Internally uses s pring and hibernate  . Manages Database connection pool internally. The basic operations of create, read, update, delete (CRUD) operations Service Builder Generate  -api  IT MAINLY CONSISTS OF INTERFACES -service IT MAINLY CONSISTS OF implementations Note:   *Util  classes are generated for backwards compatibility purposes only. Your module applications should avoid calling the util classes. Use the non-util classes instead–you can reference them using the  @Reference  annotation . You can modify any  *Impl  class Service Builder generates. The most common are  *LocalServiceImpl ,  *ServiceImpl  and  *Impl . If you modify the other classes, Service Builder overwrites the changes the next time you run it. Whenever you add methods to, remove methods from, or change a method signature of a  *LocalServiceImpl  class,  ...

  Headless Architecture Liferay's headless APIs allow RESTful interaction with Liferay DXP resources . Backend resources are not tightly coupled with Frontend. Backend apis are machine  readable  and uses Open API . Any frontend tech like react etc can be used . We can leverage this across channels. Example - you want to show the same Blog etc from Liferay in multiple channels so when u use Liferay Headless api you dont need to keep changing all the channels and UIs. References :- https://www.youtube.com/watch?v=mP_6GgQOxIg