rvsunilkumar

1. Mule4 Generate Custom policy template using maven Archetype. Add the following profile to settings.xml(.m2/settings.xml), this is to recognize the maven archetype repo location. < profiles > < profile > < id > archetype-repository </ id > < repositories > < repository > < id > archetype </ id > < name > Mule Repository </ name > < url > https://repository-master.mulesoft.org/nexus/content/repositories/public </ url > < releases > < enabled > true </ enabled > < checksumPolicy > fail </ checksumPolicy > </ releases > < snapshots > < enabled > true </ enabled > < checksumPolicy > warn </ checksumPolicy > </ snapshots > </ repository > </ repositories > </ profile > &

  1 – Codebase One codebase per service, tracked in revision control; many deploys 2 – Dependencies Explicitly declare and isolate dependencies. 3 – Config Store configuration in the environment 4 – Backing Services Treat backing services as attached resources 5 – Build, Release, Run Strictly separate build and run stages 6 – Processes Execute the app in one or more stateless processes 7 – Data Isolation Each service manages its own data 8 – Concurrency Scale out via the process model 9 – Disposability Maximize robustness with fast startup and graceful shutdown 10 – Dev/Prod Parity Keep development, staging, and production as similar as possible 11 – Logs Treat logs as event streams 12 – Admin Processes Run admin and management tasks as one‑off processes