Microsoft Azure alternatives and competitors

I have a single 4GB model Linode and I use it as a personal server. I originally set it up to act as an email server, just for my own personal vanity domain. I don't use it for that anymore, but it's proved to be useful for many other things.

Right now, I run a Minecraft server on it and I also use it for a little bit of software development. I also use it as a jump host, if I need a stable place to SSH from my laptop to get to other online resources. It means that I only have a single point that I go through to get to the other stuff that I need.

I would say it's very important that Linode offers a relatively small, but well-focused set of cloud computing services because it differentiates them from AWS, Azure, and Google Cloud by being focused and by having a more personal touch. I could probably get the same compute power for a little bit less from other providers, but the value of the continuity and the high quality of support is worth it. It's rare that I need to reach out to support, but when I do, the support is great.

Even though I use it for personal use, some of the things that I use it for are in a software development capacity. For example, the ability to experiment with running my own Mercurial server, Git server, and source control servers on this machine have leveled up my own knowledge of those products in a way that I think a more managed solution wouldn't. Having the tools in-hand of just a Linux box that I can play with, and that I can wipe and reimage at will, is more useful than a physical machine by virtue of that virtual rewriting. It is also more useful than a more abstracted managed service, just in that I can get my hands dirty and do rapid experimentation.

Linode has helped me to accelerate innovation and even though I'm not using this in an enterprise way, it has improved the way I innovate with respect to personal stuff. For example, it has helped with the things that I'm trying to learn and the things that I'm trying to do. Setting up a Minecraft server is a good example of that. Being able to read some of the documentation that Linode has about setting up a Minecraft server on your VPS, and just learning and figuring stuff out, has been valuable.

The most valuable feature is the static IP address, which has been very helpful for being able to log into the same address over the course of more than a decade.

Another useful feature is being able to have multiple system images that I can play with. I mostly use Ubuntu Linux, but if I want to play with a new version of Ubuntu, I can pretty easily add that. It's been super useful to upgrade my system over the years.

I just recently started using the Object Storage and Backup features, as well. Having good backups for peace of mind and disaster recovery is very nice as well.

Object Storage has been key, for me. I don't have a strong notion of exactly when Linode introduced Object Storage, but it's been very useful for me, for instance, in backing up my Git server, in addition to the whole node backup. The fact that I can interact from the command line with the Linode Object service to back up specific datasets, is super cool. I know they didn't have it when I first started using Linode and I think it's been introduced fairly recently, within the last couple of years.

The Linode documentation is superb. 

I would like to see more seamless integration with backup, although it's pretty easy to do.

Having more on-demand features would be helpful. For example, if for a little while I wanted to have four Linodes instead of just a single one, it seems like it's a little bit more difficult than spinning up an EC2 instance in AWS. It isn't a lot harder, but it could be improved nonetheless.

I have been using Linode for more than a decade, since 2008 or 2009.

The stability is excellent. It's very rare that there is an interruption in the service. I think that the reboot notices that I get, that aren't related to me doing stuff, are less than one a year. I think, in some cases, it's been four or five years between needing to have any kind of stability-related events on the machine. I can't think of any outages in the entire course of me using it, that anything with any kind of significant impact.

Part of the thing that I value about the single Linode that I have is that it is a very steady, stable known quantity. I don't have to worry about all the institutional weight that I do with interacting with AWS, which I do a lot from work.

Thinking about it from an operations point of view, I think that I would have a bit of a harder time scaling in Linode than I would in AWS, but not a whole lot harder. Given the Kubernetes support, I would imagine that that makes the process even easier. That said, I have not tried Kubernetes so I really have insufficient data to be sure.

It's not likely that I'm going to significantly increase my usage in the future. I might bump up to a higher size if I find that I need more CPU or RAM. Or, I might play around with having two to four Linode nodes. But beyond that, it's unlikely that I'm going to expand much.

I will definitely keep using Linode for as long as it is as stable and reasonably priced as it is, but at a steady one machine for my personal purposes.

The support from Linode is great. All of the times that I've reached out, it's been through email or through the web portal. It's always felt good and it felt like the person responding understood what I was asking about and solved it very quickly.

In terms of flexibility and overall responsiveness, the support is very good to excellent. Certainly, everyone that I've interacted with, in the fairly rare occasions that I do need support, have been very knowledgeable about the product and very good at understanding what issues I'm having and how to solve them.

I would say compared to AWS, AWS support varies a lot in terms of responsiveness and whether you've got a paid support plan. Sometimes, it does take a fair bit of back-and-forth with AWS support to get to the crux of the problem. I've never felt that back-and-forth was as necessary, that we get to the crux of the problem and solve it much more quickly with Linode.

Prior to using Linode, all of the machines that I had managed were all physical. I had my own personal machines and machines that I built for work, but they were all physical PCs or other architectures that I had to actually open up a case, and if I needed more RAM, I had to put the sticks in myself.

In comparison to a physical server, Linode has definitely saved me money. I never want to build a server again. Basically, if you build a physical machine and it is obsolete within two to five years, you've got to buy and recreate the whole thing again. Generally, the hardware is going to get cheaper over time, but I think that unless I were really putting a microscope on getting the cheapest components for building, Linode will cost less.

In some contexts, albeit not mine with just one or a few machines, it would make sense to build them. However, not having to worry about it and just letting Linode take care of the hardware upgrades is probably saving me money. I don't know if it would save a very tightly tuned hardware IT team money, but that's a completely different scale than what I'm looking at.

Linode was my first experience with virtual cloud servers and virtual machines, in general. Not too long after I started using Linode, I did start doing more with VMware, with an on-premises, physical server hosting multiple virtual machines. It was not too long after that when I got into AWS for work.

I found the initial setup to be fairly straightforward. It's so long ago that the details are fuzzy but I recall that I set up the account, chose names for things, picked which size I wanted, and then launched it. Within, what at that time, was an astonishingly short amount of time, I was able to log into it. It's just gotten better from there.

I didn't require an implementation strategy, although I think that's peculiar to using it as a single thing for personal use. I had the notion that I wanted a persistent Linux machine that was always on, and that I could get to from anywhere, and Linode seemed to fit the bill.

Over the years, I've used it for a lot of different purposes and it's adapted well to that. So I would say in this case, I didn't need a whole lot of planning. If I were to use Linode for a more complex deployment, I would want to plan it out, figure out what the costs are, figure out the network topology, and the other relevant details.

Linode offers worldwide coverage via multiple data centers, although I don't personally need that. It's a very attractive feature for sure, but since I just have the one virtual private server and it's just for me and for my friends connecting to it, I want it to be geographically close to me to have a low ping. I think it's located in New Jersey, and that's good for me, being in New England. While global coverage is not super important to me, in so far as it contributes to the health of Linode in general, I'm all for it.

The pricing model is simple, and that's one of the reasons that I've stuck with Linode for so long. When I was on the $20 Linode, I knew for a fact that on the first of every month, my credit card would get charged $20. That meant my Linode was available constantly.

At this point, I'm paying more like $35 per month for a slightly bigger machine, and the backup, and the object service. But again, I know that it's exactly $35 every month and I can budget for it. The simplicity and the consistency of that billing and pricing are quite valuable to me. Whereas with AWS, it's a crapshoot. The on-demand pricing means it's flexible and I only pay for what I use, but it's also much less predictable.

It is tough to determine whether using Linode has saved me money compared to what I would pay with other cloud providers. I don't think it has on a pure numbers basis, but in opportunity cost and higher-level budget planning, I think that the consistency probably has saved me money. I would have spent more time trying things, allocating things that I might not need, and so on. Ultimately, it saved me capital in the long run but it is not necessarily something that I can put a dollar figure on.

In comparison to everything else, predictability is the key aspect of the pricing model. With it being a known quantity that I can budget for every month, it frees up brain cycles to do everything else.

In my personal capacity, at this point, I have my Linode and I have a personal AWS account, and I use them for different purposes, but to similar degrees, or similar magnitudes. I find that just looking at it from a strict CPU and RAM horsepower perspective, EC2 is just marginally cheaper, but there are different features that I value in different places.

I took a brief look at some other things like Azure, Google Cloud Engine, and DigitalOcean, and I found that when I was looking, and this was probably about five or six years ago, that a lot of things that I wanted were pretty comparable in terms of capabilities and pricing. A lot of it came down to what I valued, in terms of the positioning, and support, and documentation, where I very much like Linode's documentation, especially, and support.

Of the others that I evaluated, DigitalOcean seemed the friendliest. And then, AWS and Azure were the behemoths, the 800-pound gorillas in the room.

The biggest lesson that I have learned from using Linode is the oldest lesson, which is just that a virtual cloud server has the availability and the flexibility that I couldn't get from physical at the time, or even now, for that matter. It's a key component in having something that's useful, having a machine that you can log into and do things on, in a consistent way, regardless of where I am or even what machine I'm connecting to it from.

My key advice for anybody who is looking into Linode would be just to dive right in. Pick it up and play around with it and if you find that it's not for you, try something else. But if you find that you love it, keep going.

In summary, Linode is a good product and I've been extremely satisfied with it for exactly the purposes I use it for. I have been pleased with it since I started using it.

I would rate this solution a ten out of ten.

We create applications for other companies to power HR experiences. Mostly somewhat complicated web applications, so that's where we use the SAP Cloud Platform. The web applications may have standard backend launches and use front-end technologies such as React or even the conventional SAP WiFi, so we use the SAP Cloud Platform for those cases.

Though I'm not a massive fan of the SAP Cloud Platform, it has good features, such as its integration with other SAP solutions. When integrating with SAP or even the SAP sister company SuccessFactors and other companies SAP has acquired, you also enjoy data features in the SAP Cloud Platform, such as role-based permissions and other characteristics you can import from SAP.

From what I understand, the SAP Cloud Platform is for implementation on AWS or Azure, and it's not meant to be a full-fledged cloud solution, so while using the platform, an area for improvement is that it has fewer offerings and is less flexible when compared to AWS. AWS has a lot more flexibility than the SAP Cloud Platform.

I've also used Azure in college and AWS in between, and I prefer AWS over the SAP Cloud Platform. The only reason I would ever stick with the SAP Cloud Platform is to create applications integrated with SAP or with other companies within SAP, such as SuccessFactors.

When you go into the SAP Cloud Platform web page, it's a bit bland and has relatively limited offerings. For example, there doesn't seem to be in-house MongoDB support, but I realize there's in-house support for the PostgreSQL database, so there are fewer offerings in the SAP Cloud Platform. Yes, you can always go for a database on the actual MongoDB server rather than depending on the offerings of the SAP Cloud Platform. However, it's still better to support MongoDB from the platform, so payment is consolidated, rather than going to a different location to make a payment.

Another room for improvement in the SAP Cloud Platform is the need to create an SAP subaccount if you need to use the platform unless you have an SSO login by Google or if you're using a different identity provider such as Microsoft or Google. Instead of requiring dependency on SAP, it would be good if users could use the SAP Cloud Platform even without a subaccount on SAP. For example, when hosting an application on AWS or Azure, you don't have to create an account in Amazon or Microsoft. You can still do it using Google. You can use almost anything, so I'd like SAP to improve by removing the dependency, particularly the requirement to create an SAP account to use the SAP Cloud Platform.

In the next release of the SAP Cloud Platform, it would be exciting to see more in-house support for many new features, similar to what AWS or Azure offers. It could be different types of systems instances, though that could already be there, so I'm unsure about that. Including MongoDB support on the platform similar to what's offered on AWS would be great because I use MongoDB a lot, and I've even used it for personal tasks, so I'm a bit biased. For example, in AWS, you can have a MongoDB system with 750GB and limits and calls per month. It would be nice if MongoDB support is available in the SAP Cloud Platform.

I've been employed in the company for fifteen months. I was a freshman out of college and employed here, so I've used the SAP Cloud Platform since joining the company.

The SAP Cloud Platform is stable, and I haven't had many issues with it. My use case for the platform has been mostly limited, though. Hence, I'm unsure if that stability I'm experiencing applies to every single scenario, but whatever I've used the SAP Cloud Platform for so far seems pretty stable.

I've never contacted the technical support for the SAP Cloud Platform, as I only have limited experience with it.

As many of our applications require SAP data and integration, we went for the SAP Cloud Platform, though we also have a separate AWS solution.

I don't have information on how straightforward or complex the SAP Cloud Platform setup is because the technical staff did it for the company. I'm a developer who builds and deploys applications, and I also manage the SAP Cloud Platform a bit, but I'm not involved in setting it up.

Cost-wise, I'm unsure of how expensive the SAP Cloud Platform is.

I'm a site developer, so I'm not technical enough to know which version of the SAP Cloud Platform I'm using.

SAP Cloud Platform is deployed on a public cloud, not on-premises. It's on AWS, with BTP.

In the company, the number of people who have access to and use the SAP Cloud Platform is close to ten. Not everyone has access to it. Only a small group of people has access to the SAP Cloud Platform.

The only advice I would give anyone planning to use the SAP Cloud Platform is more of a personal opinion on how I've used the software. I'd advise you only to use it if you have dependencies associated with SAP. Otherwise, please go for a more generic cloud provider such as AWS or Azure. I prefer Azure over AWS because of the more straightforward and more organized UI and console compared to AWS. Azure is more user-friendly than AWS.

My rating for the SAP Cloud Platform is seven out of ten because it's mostly stable, though I have no information on its licensing costs. After all, that's handled by someone else, so I'm unsure if the platform has any hidden charges. Its integration with SAP solutions is impressive, so if you have applications that utilize SAP data, the SAP Cloud Platform is pretty good. I'm taking away three points from the perfect score of ten because the platform still lacks many features and is very basic compared to the offerings from competitors such as AWS and Azure.

My company has a partnership with SAP.

Our specialty is insurance software. We were primarily vendors for software licensing, but we've transitioned our product to the cloud in the last two years.

The deployment depends on what a client wants. We use public clouds for clients that are willing to take our products as a SaaS model. For the ones that are on-prem, we split the load between the core platform, which is on-prem, and non-essential services, which are on the cloud.

I head the sales and marketing team. So, specifically on the feature set side, multi-tenancy is the one that I'm most familiar with. It's also the one that we found to be the most beneficial to us because it allows us to take clients that have multiple sites. For instance, one of our larger clients, which is a bank based out of South Africa, has offices in multiple countries. It allows us to multi-tenant each and create a tenant for each country within multi-tenanted architecture.

The biggest challenge I'm having with the cloud offering is the sizing. So, pricing becomes difficult. The sizing challenge is in terms of being very clear on how your data growth or your requirements would be. It becomes a bit difficult to be able to ensure that there's enough future proofing in what you've signed. At the same time, the whole idea behind the cloud is to be able to pay for what you use. You don't want to pay for something that you're not using.

It has been two years. 

All our clients are enterprise clients. We don't have any small clients.

The main challenge that we have with scalability is the opacity and the pricing. Pricing becomes a challenge because you're not very clear on at what point in time you'll be breaking or you'll be exceeding the size you already acquired. That is the challenge, but Oracle powers some of the biggest cloud platforms in the world, and so do AWS and Azure. All of them have the ability and skill to run very large platforms. 

They have an office locally. Amazon has only just started an office locally. Microsoft has been here for a long time. We've been Oracle Partners for 22 years, So, we're familiar with them anyway.

I know it's very straightforward. Microsoft Azure, Oracle Cloud, and Amazon AWS have some sort of out-of-the-box packages that you can purchase. Oracle also has a sandbox environment that they can provision for you to be able to set up your operation just to try it out. So, the setup is straightforward.

Its pricing is complex, but as partners, we can get away with quite a bit of discounting because we deal with them directly. 

I would rate their pricing probably a one or two out of five because they're quite expensive. Microsoft Azure will probably be the cheapest because depending on the Microsoft product that you have, they have some sort of bundling. There are things that they give you to get you onto Azure. AWS is probably somewhere in the middle.

We work in a very narrow space. Our specialty is insurance software. We have an insurance ERP. We are an ISV. So, we make our own software. In the sub-Saharan African market, we're, in a way, the largest vendor. So, our recommendation for the clientele that we serve would ideally be Oracle. 

There are a lot of data laws that are being enacted. Kenya is one of the big ones enacting data access and data sovereignty laws, which is probably denting a lot of cloud offerings. However, there are a lot of co-located operations where people are providing data centers within the country. The in-country cloud providers, such as MTN and Liquid Intelligent Technologies, give you a lot more flexibility. In that scenario, you get a lot of flexibility in hybridizing the cloud setup that you have, and all three of them would work pretty much the same way. From a Kenyan or African perspective, Oracle and Microsoft have a very good footprint across all the countries we operate in. We're in eight countries now. Amazon AWS is only just starting in Kenya. I don't know if they're anywhere else. They might be in Ghana, Nigeria, and South Africa. So, they would have a hub-and-spoke type model in terms of how you'd be able to support it. If I were to recommend anything, it would be Oracle Cloud and Microsoft Azure.

I would rate Oracle Cloud a nine out of ten.

While I cannot say for certain, I believe that we are using the latest version. 

We primarily use the solution to rent servers for storing certain commercial applications.

I especially like the flexibility and scalability of the solution. It is totally scalable. 

While feasible, custom configuration will be more time consuming than standard, although we have not encountered many instances which required us to seek support or advice.

I believe we have been using Amazon AWS for more than 10 years.

The solution is absolutely stable. This is one of its best features. 

The solution is absolutely scalable. 

Amazon allows us to scale up and then down, something important to one of our customers who was in need of temporary increases in the throughput provided to the servers. This allowed us to meet the client's needs for the days or weeks that they required more dynamically located servers, after which we were able to scale down. This we were able to do through Amazon. This was difficult to accomplish beforehand, as the client had private servers for which he was forced to buy machines which he would subsequently keep. 

I cannot comment on Amazon's technical support, as we have not made use of it. 

We did use other solutions prior to Amazon AWS. We made use of local service and dealt with projects involving Google and Microsoft. We also used Microsoft Azure. 

Not long ago  we used Microsoft Azure, though this is necessary with some of our projects. We have different projects which vary with the customer's specifications. Some utilize Azure, although most require the use of Amazon. 

When comparing Microsoft Azure with Amazon AWS, I do not see much disparity. It really comes down to a business choice. If the customer is familiar with Microsoft, then the testing team maintaining the product will need to be acquainted with it as well and its ongoing use is required. Similarly, Amazon will continue to be employed if this is already the case. As such, the difference betwen the solutions does not come down to considerations of a technical nature as they are largely similar. The primary consideration is one of business, the use of one solution and provider over another. 

When it comes to standard configuration, the installation is quick, usually taking one or two days to complete. Custom configuration, while feasible, takes somewhat longer. So far, we have not had many instances in which we required support or advice concerning custom configurations. 

The technical team would be in a better position than I to address any technical issues involved in the setup. From my perspective as a project manager, I feel what we have to be sufficiently good. There is much advertising, information on the advantages of the product and guides available. 

Installation was carried out by our own internal integration team, not externally outsourced. I did not handle it myself. It was done by a team specialist. 

The technical team responsible for the deployment consists primarily of engineers. 

I cannot comment on whether we have seen an ROI, return on investment, as I do not possess this information.

The licensing cost varies with the project involved. Certain projects run around $6,000 per month, some less and others more. We handled many projects, each with its own complexities and specifications. The price ranges of the licenses varies with the complexity of the project. 

Broadly speaking, there is a need to rely on specialists for properly setting up one's accounts and addressing his needs. This is not specific to Amazon, however, but is something prevalent with all providers.

I have assumed the role of both customer and integrator. In the past, I worked as a project manager with different projects employing Amazon products, services and software. 

For the most part, the solutions I used have been public, not private, such as AWS cloud. 

The number of users of the solution varies with the individual project. This can range from 20 to 200 to 500 users. 

Our teams have undertaken every role, be them architecture, development, design or testing. They are all internally integrated. 

I am a fan of Amazon products and generally recommend them to others. Of course, we employ Azure and Google products when the customer specifically requests these. 

Since all products have room for improvement, even when this is not apparent to me, I rate Amazon AWS as a nine out of ten.

Right now we're using two cloud platforms, one being Oracle Cloud Platform and the other Microsoft Azure. We've been using Oracle Cloud Platform since 2018 and Azure since 2015.

We use Oracle Cloud Platform with the OCI Infrastructure as a Service offerings, and we're essentially using it for the compute instances and nothing else. We have deployed some servers running Oracle Linux which are being used as our main development environment. Then, we also have servers for our UAT (User Acceptance Testing) environment. Neither of these use cases are for production environments, and they are only used for development and testing.

To access Oracle Cloud Platform, we have a VPN site-to-site connection from our site to Oracle Cloud. We don't have the FastConnect option because we don't have a very good reason to use it.

As for users, we typically have around 20 people who are connected to the Oracle environment and who do their work on it. Regarding maintenance, we have three people on technical staff for that, who are DBAs and architects.

It hasn't improved our organization in a direct, or highly visible, way because we only use it for development and testing. However, I enjoy the ease with which we are able to deploy Oracle Linux server instances and other Oracle products. 

I like having the ability to easily run Oracle Linux server instances and to deploy Oracle Middleware and WebLogic servers. Oracle's Infrastructure as a Service products are also very useful, and we're using those right now within Oracle OCI.

I think that there could be a more user-friendly environment when it comes to the options that Oracle presents through the Oracle Cloud Platform.

Also, when you compare it to Microsoft Azure Marketplace, there aren't as many options to choose from, and some features are not available in some operating systems. In particular, I'd like to see more readily-available features such as Fusion Middleware as a service, in the same way that they have WebLogic as a service within OCI.

I have been using Oracle Cloud Platform for the last three years.

It's very stable, especially when it comes to accessing the Oracle Cloud Platform through VPN.

It's very scalable and we haven't had any issues in that regard.

We have not previously used a similar solution to Oracle Cloud Platform. We started with Oracle Cloud Platform because we were already using Oracle products and we decided that deploying Oracle products on Oracle Cloud Platform would be a more sensible idea than deploying on other cloud solutions.

The setup was very straightforward and it only took one to two days for the initial deployment.

We used Oracle consultants through Oracle's ACS, along with three technical personnel including DBAs and architects.

On a monthly basis, we pay around $2,500 for licensing fees, with no additional costs. We do pay extra licensing for other on-premises solutions, but these are not related to Oracle Cloud Platform.

We're not using that many products within Oracle Cloud Platform, but nevertheless I can recommend it. Especially when it comes to the Database as a Service, which we use a lot. I can easily vouch for that if you are looking for good database performance.

In addition, if any companies or clients are currently using Oracle Database on-premises, I can certainly recommend that they migrate to Oracle Cloud Database. 

I would rate Oracle Cloud Platform an eight out of ten.