I'm working with a small backend team, and we're using AWS technologies like RDS and Lambda. What's the best approach for two developers to work simultaneously on this setup? Should we each have our own dev RDS instances running, or is there a way to develop locally without needing RDS? Any tips on managing this setup effectively would be appreciated!
5 Answers
The workflow for a small team usually involves each developer committing their changes to their own branches in git. When the code is ready, they'll merge it, which is straightforward whether or not you're using AWS. Just keep an eye on each other's changes to avoid any merge conflicts.
For sure. If you're making database changes, just coordinate to avoid overwriting each other's work!
If you're worried about the two developers clashing over database changes, the best practice is to script those changes through Continuous Integration (CI). This way, if both of you are working on migrations, it limits the risk of stepping on each other’s toes. Having a single test RDS that mirrors prod can also work, just have good communication around it!
For sure! And if both devs are working on Lambda functions, they can just test in the shared Lambda until they're ready to deploy.
I've worked on bigger teams like this before, and it usually comes down to clear messaging when changes are being made.
Another approach is to set up separate AWS accounts for each developer under the same organization. This way, everyone can test their changes without stepping on each other’s toes. Plus, you can run your RDS locally in Docker, which is super efficient!
That’s the way to go! Using local containers makes things a lot more manageable.
Totally agree! Keeping resources isolated helps avoid conflicts.
Ideally, you want to avoid having separate RDS instances for each developer. Instead, you should have local development environments that replicate the AWS setup. RDS is just a managed database that you can mimic locally with something like PostgreSQL or MySQL. Also, you can use AWS SAM to run your Lambda functions on your local machine. It makes local development smoother!
Yeah, running locally is key! Having Docker containers for both your database and Lambda function can streamline the process and avoid conflicts.
But I think you should still have some sort of test environment. It's risky to work directly on dev without proper checks.
Honestly, with a small team, simplicity is key. Just have one dev and one test environment that reflect the production setup. Most of your work won’t involve major infrastructure changes. Communicate when you’re planning updates to things, and you’ll be good to go!
So true! I’ve seen teams overcomplicate things when they don’t need to.
Communication is everything in small teams. A quick Slack message can prevent a lot of issues!
Exactly! Just communicate any major changes to the team so everyone is on the same page.