Member-only story
DevOps in Cloud
As projects grow more and more complex you often hit roadblocks you did not see coming. Luckily most software projects run into similar issues and generic solutions are available to take care of them. This article is my take on how code could be structured to develop with minimum chaos within and across teams.
- Environments/Accounts
In a typical project you would have four to five environments.
dev — used for development
test — used by testers for functional testing
uat — used for user acceptance, integration and load testing
prod — for your production environment
shared/infra — for pipelines, git etc
2. Repository Structure
The application stack may have several repositories such as for applications, infrastructure code, databases and libraries. In order to keep them all organised, the repository structure should be clearly separated :-
- Applications
- Libraries
- Application/Modules
- Application/Libraries
