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)
F5 Distributed Cloud Network Connect
Score 9.0 out of 10
N/A
F5 Distributed Cloud Network Connect is a solution used to more easily and securely network across public clouds, hybrid clouds, and edge sites via an agile SaaS-based service. Users can rapidly connect instances deployed across multiple cloud regions and/or different cloud providers using Distributed Cloud Network Connect and its automated provisioning, integrated service stack, and end-to-end visibility. Cloud instances will be connected in minutes and always visible for rapid troubleshooting.
N/A
Pricing
Azure DevOps
F5 Distributed Cloud Network Connect
Editions & Modules
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)
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.
F5 Distributed Cloud Network Connect provides Intent-Based Policies and Unified Operations which is equal for all customers . Complexity is eliminated and common services and rules are provided across clouds and on-premises settings with the help of an integrated service stack and automated deployment. There is nothing specific scenario where we found that it is not suitable for current environment.
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.
The support model needs a quite a bit of work. I personally have experienced an outage on the platform. due to mis-configureation Although the outage was due to engineer error it took over 2 hours before we were able to speak to an engineer
Proxy v2 protocol to allow our organization to capture and view the source IP address
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.
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.).
Overall, F5 Distributed Cloud Network Connect is responsive and has many features. There is minor clunkiness in how certain scroll bars are layered. This may cause some adverse experience when trying to manage this product through a zoomed browser. Page loading and refresh timers were all very much responsive. There is a good amount of feedback from the interface as well.
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.
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.
Similar, very similar to both. The main difference has been existing relationships with F5 as a partner and future potential for layering on future advanced services on top later. Often a difficult sell initially as both competitors have larger networks, but often can outclass Akamai in terms of capabilities, when against Cloudflare it is most difficult when no existing relationship exists to not consider Cloudflare's larger footprint.
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.
