We want to use git for SCM of our database codes. However, our whole database objects count is around 40000 objects.
Do we need to create a Stash repository for each object? (I think so, since every object can be versioned separately)
How Stash will perform with more than 40.000 repositories performance-wise?
I'd suggest you group your PLSQL objects in some way. Managing 40,000 repositories doesn't sound at all appealing, irrespective of the performance impact.
The most extreme, but probably viable, case would be to put everything into one repository, just as you would any other coherent set of files. You can change, commit and track changes to each object (or sets of them) using git.
The Stash codebase, as a comparison I have to hand, tracks over 8,000 files and it's by no means the largest repository around.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot