Cosmos DB offered better scalability. In Azure SQL, we had to carefully manage the storage tier, switching back and forth based on needs. But when we first implemented Cosmos DB, we had a good understanding of the required data volume over the past three months. This helped us select the appropriate tier because we had those figures. If we had done it the other way around, it would have been much harder to estimate the data accurately. While you can get a rough idea, whether it works out in practice is more of a hit-and-miss approach, which we have already experienced with Cosmos DB. We applied the knowledge gained from that exercise to build a similar solution over Azure SQL. On the DevOps side, our team consisted of five members, ranging from senior to junior roles. We would raise requests for specific services needed in the development environment. The process typically takes three to five business days, including all necessary approvals, from submitting the request to receiving the resources and verifying access.
