Hi @HPM- ,
With AEM as a Cloud Service (AEMaaCS), you have the option to leverage Remote Development Environments (RDEs) rather than local environments for your developers. Here’s an overview of the pros and cons of using RDEs compared to local environments, which should help you make a well-informed decision for your scrum team.
Pros of Using RDE in AEMaaCS
Consistent Cloud Alignment: RDEs are specifically configured to mirror the cloud setup, which ensures that the development environment is fully consistent with the production environment on AEMaaCS. This eliminates discrepancies in configuration or code deployment that might arise from local setups.
Simplified Maintenance: RDEs remove the need for local environment configuration and dependency management. Each developer works on the same cloud-based instance, meaning updates, environment configurations, and versioning are managed centrally, reducing local troubleshooting and setup time.
Team Collaboration: RDEs enable real-time collaboration. Multiple developers can work on the same environment simultaneously, seeing each other's changes and ensuring code sync across the team without needing to push updates to a version control system and then pull those changes locally.
Scalability and Resources: In cloud development environments, scaling resources on demand is easier. This is especially beneficial when running high-resource operations that might be limited on local machines, like batch content processing or heavy integration testing.
Reduced Local Machine Dependencies: Using RDEs reduces dependency on specific machine capabilities, OS configurations, or storage limitations, which is helpful for teams with varied hardware setups.
Version Control and Traceability: Cloud environments support better traceability in terms of environment versions, allowing rollbacks and creating a unified development history that’s accessible to everyone on the team.
Cons of Using RDE
Latency and Network Dependency: Cloud-based development can sometimes introduce latency, especially if team members are geographically distributed or have variable network speeds. This can make local testing and iterative development feel slower compared to a local setup.
Potential Resource Contention: Since RDEs are shared across developers, heavy workloads from one team member could impact others, depending on how the environment is configured and managed.
Limited Offline Access: RDEs require a continuous internet connection, which can be a disadvantage for developers who work in areas with unstable connectivity or need to work offline.
Debugging Complexity: Certain types of debugging or intensive local experimentation may be more challenging in an RDE. Local environments often provide more flexibility for developers who need to test and debug code changes outside of a centralized setup.
Performance Variability: In some cases, tasks performed in RDE may not be as responsive as on a local machine with dedicated resources, especially for intensive development tasks or local previews.
Recommended Considerations for Your Team
Hybrid Approach: Many teams benefit from a hybrid model, where RDEs are used for quick deployment and unit testing before actually deploying code to DEV for QA testing in an environment closely aligned with production, while developers can also use local instances for rapid development and debugging tasks.
Resource Allocation and Permissions: Ensure that your RDE is configured to provide adequate resources to each developer, and that access permissions are in place to prevent accidental changes to shared configurations.
Tooling for RDE: A good DevOps setup that automates deployment, environment creation, and teardown processes can make RDE usage smoother, especially if your team uses continuous integration/continuous deployment (CI/CD) systems that sync well with AEMaaCS.
Overall, RDE can indeed be a viable and efficient option for a development team, especially for a cloud-aligned product like AEMaaCS.
However, on my several projects we didn't use RDE envs, because we were good to wait development pipeline completion (30-45 mins). During the very active development phase we disabled pipeline auto-run on every commit to develop branch. When we merge several tickets at once, we executed pipeline manually. Once active development phase is over, we enabled auto-deploy on every commit to develop branch. Here you can find scripts how to update your local instances: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aemaacs-what-s-the-best-wa...
So, we had the following setup:
- Local instances - for development team.
- Dev AEMaaCS instance - for Dev/QA testing
- Stage AEMaaCS instance - for Release/UAT testing
- Prod AEMaaCS instance - for Prod.
