If there are ten developers with 10 feature branches are they going to be running 10 instances of Oracle with their own “branches” of the stored procedures?
And then copy “enough” data on their computers to have a realistic test and make sure you have some type of script so sensitive data isn’t on their laptops and ensure schema changes are constantly propagated to each developers workstation. This isn’t even mentioning if you have a commercial database like Oracle where you have to deal with licenses.
And how do you merge changes and do rollbacks?
Not to mention the whole
GetCustomer_1
GetCustomer_2
GetCustomer_3
Where code is copy and pasted and modified slightly.
It’s much different. As someone who is a long time developer who also deals with the “DevOps” side of the world. I never design architectures of the former (development) without thinking about the latter from day one.
You can’t just wave your hands and throw it over to the “DevOps” folks. Doing so is kind of just the opposite of what “DevOps” is suppose to be.
Yes, learn to use multiple schemas and instances, just like using multiple deployments into Apache, Tomcat, IIS,...
Or even better, join the hype, and use containers with volumes configured for each feature branch.