Development life cycle using Rapid Development Environment

Transcript

Now, we have learned how to set up and use Rapid Developed Environment or RDE for short. Let’s review the new development to deployment cycle to have a business impact and deliver value with speed. You complete your feature or hotfix via the development R files such as HDL, Dialog, Sling models, OSJS services or configurations. Next, you verify these changes locally on AEM SDK, making sure it passes all unit test and acceptance criteria. Then commit these changes to the GitHub repository. If needed, collaborate and communicate with the team to use an RDE. Then deploy the AEM project or individual files to the RDE from your favorite IDE. Then verify changes on RDE, make sure there are no breaking changes. If needed, repeat previous steps in case of an issue. Then run the desired cloud manager pipeline or request your deployment manager to do the same. Then verify changes and complete the handoff. Now you are ready for the next feature development.

Transcript

Let’s talk about the benefits of RDE. Faster development cycle. RDE provides a simplified and faster setup for AEM cloud deployments, enabling developers to start coding and testing immediately. Next, reduce downtime. RDE eliminates the need for a long-running build and deploy processes. Next, better testing. RDE allows developers to test their changes in a near-production environment, giving them more confidence in their code and reducing the likelihood of unexpected issues when deploying to dev, stage, or prod cloud environments. Also, improve collaboration. Multiple developers can use a single RDE instance, making it easier to collaborate on code changes and debug issues. Lastly, increase productivity. RDE streamlines the development process and eliminates many of the manual steps required for deployment, freeing up developers’ time to focus on coding and testing. I hope this was helpful on how to get started with RDE and accelerate your time to market. Thank you and let’s keep learning.