Basecamp vs. Microsoft Azure

Basecamp is a wonderful tool for teams of varying degrees of technical knowledge, teams managing lots of different types of "agifall" and waterfall projects, and teams that are remotely distributed. It's probably less useful for more strictly agile-focused development teams, compared to other more flexible software applications like Jira and Asana.

Incentivized

Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.

• Task management - It is very easy to add, organize and discuss tasks within Basecamp's interface.
• The "Campfire" function is great for communicating when you just have a quick question for someone on the team.
• Notifications - Basecamp lets you decide how often and about what you'd like to be notified. The ability to respond to messages in Basecamp directly via email saves a lot of time.

Incentivized

• Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
• You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
• The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
• The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.

Incentivized

• High Learning Curve. It's true that it can be easy to use, but to use well and effectively takes some time to learn. It's recommended to have an agreed-upon system in your team of what tools to use and when.
• Notification Overload. If people aren't careful they could send a notification to everyone when only a couple people were meant to be prompted. And since emails are sent by default, you could have your mailbox overloaded with unnecessary updates. This is where it takes a bit of training in your team to have an agreed-upon system.
• Lack of organization with Archived Projects. I will often need to reference an archived project to make a new one, but there is only a list of archived projects in alphabetical order, with no way to organize by archive date, or even search.

Incentivized

• The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
• The documentation needs to be improved, and some advanced configuration options require research and experimentation.
• Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.

When I bring new people onto a project, it's immediately obvious how to use Basecamp. I don't have to worry about teaching them the features or walking them through it, it's just incredibly user-friendly. For this reason, I'll continue to renew my subscription even as new people are brought onto production jobs or the client changes.

Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.

It is easy to use, even for clients who have no experience with the platform. It can only get a little cumbersome to ensure that a client can't see certain documents you might want to keep in the Docs & Files folders. And sometimes, getting a client to actually use an unfamiliar platform can be a challenge.

Incentivized

As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.

Incentivized

I've never experienced downtime while using Basecamp, or been unable to access it when I needed it. That's not to say they've never had downtime, but I've been lucky enough not to encounter any, and I work odd hours, including late nights when maintenance is often undertaken.

Incentivized

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

Incentivized

For the many reasons I've given, Basecamp is a very strong program. There are a few features I can imagine that might make it even better, but I don't have a basis for comparison to be able to say that there is definitely a better one out there. I've noticed that Basecamp has evolved a bit from the time I started using it until now, so that makes me think that the producer of this program values it and believes in continuous improvement. If you could use the features offered by Basecamp, I would think you could use it with confidence.

Incentivized

We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!

Incentivized

Decide the process before implementation - i.e. when it's due 8/9 does that mean 8am, noon, 5pm, 11:59pm? Check your to-do list frequently Set-up templates - just not with the dates (they can be funky)

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

Pretty good, but [Basecamp] has its drawbacks. Honestly I find the interface non-intuitive and sometimes have trouble figuring out how to change the status of a task. Perhaps it has something to do with the way it was originally set up by the admin, but I'm not sure. I liked Jira's drag and drop obvious functionality, but the project management side of the software was lacking. Smartsheet has excellent project management functionality, but the task management isn't as good.

Incentivized

As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.

Incentivized

• It has saved me time when having to get the same message out to multiple restaurants
• It has helped us make smarter operational decisions because we can all collaborate on an answer in a shorter amount of time (instead of calling a meeting!!!)
• The calendar function allows us to plot out our marketing agenda for the month and add/change it together as needed. The chef will post his recipe, the managers will cost it out, the social media manager will post pictures on it, and ultimately we will get that information out on an info sheet to the staff by printing the page.

Incentivized

• For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
• DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
• Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.

Incentivized