Microsoft's Blob Storage system on Azure is designed to make unstructured data available to customers anywhere through REST-based object storage.
$0.01
per GB/per month
Azure DevOps
Score 8.2 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Azure Blob Storage
Azure DevOps
Editions & Modules
Block Blobs
$0.0081
per GB/per month
Azure Data Lake Storage
$0.0081
per GB/per month
Files
$0.058
per GB/per month
Managed Discs
$1.54
per month
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Writing the Docker Images, Storing them in Azure Container Registry and then Deploying onto Azure Kubernetes Services is an Easier process which no other software/product is currently providing in the market. Best till date in terms of End to End deployment and maintaining …
In Azure, it is the storage to use, and in my view, the Blob Storage offers more, or finer-grained configuration options, than S3. So my recommendation would be to check in detail what is offered. As the Blob Storage is more or less a Microsoft exclusive product, the "interoperability" is more limited than, for example, with S3. The S3 is more widely adopted, and if you cannot exclude a migration scenario from one cloud provider to another, additional effort is needed.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Blob storage is fairly simple, with several different options/settings that can be configured. The file explorer has enhanced its usability. Some areas could be improved, such as providing more details or stats on how many times a file has been accessed. It is an obvious choice if you're already using Azure/Entra.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
Microsoft has improved its customer service standpoint over the years. The ability to chat with an issue, get a callback, schedule a call or work with an architecture team(for free) is a huge plus. I can get mentorship and guidance on where to go with my environment without pushy sales tactics. This is very refreshing. Typically support can get me to where I need to be on the first contact, which is also nice.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Azure Premium Blob offers better latency than competitors. It works best with the Azure ecosystem, and competitors lack it. Azure Blob even stands out in storage durability, providing up to 16 nines. It can have various use cases that can suit all the organisation's needs. The Azure Blob solution can also be deployed on-premises.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
