Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Microsoft Azure
Score 8.4 out of 10
N/A
Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
SharePoint
Score 7.6 out of 10
N/A
Microsoft's SharePoint is an Intranet solution that enables users to share and manage content, knowledge, and applications to empower teamwork, quickly find information, and collaborate across the organization.
$5
Per User Per Month
Pricing
Google App Engine
Microsoft Azure
Microsoft SharePoint
Editions & Modules
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Plan 1
$5.00
Per User Per Month
Plan 2
$10.00
Per User Per Month
Office 365 E3
$20.00
Per User Per Month
Offerings
Pricing Offerings
Google App Engine
Microsoft Azure
SharePoint
Free Trial
No
Yes
Yes
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
Compared with Microsoft Azure, Google App Engine requires a more complicated development environment setup. It's not as simple as using Visual Studio 2015 with Azure SDK. There are multiple IDE on the market to choose from for developing apps for Google App Engine. JetBrains …
If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as …
I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
We have settled with Microsoft Azure considered its effective administration and the ability to data visualization and analysis, together with the top-notch security/stability.
Being integrated into Office 365 and included with your subscription, there are no added costs associated with setting up SharePoint. Also being able to sync one drive and being able to open files SharePoint files via file explorer is a great added benefit.
While a little pricy at $10 a month (the other plan isn't worth it), if your team can afford it, MS SharePoint is totally worth it. It is one of the best apps for what it does, beating DropBox and Google Drive in plugins, functionality, and third-party support. And SharePoint …
The decision of selecting MS Sharepoint was relatively easy, as we have all our servers and applications in Microsoft Environments. So, by selecting SharePoint, we didn't have to worry about compatibility issues. Also, the majority of our partners are Microsoft Gold Certified, …
Obviously we still use our CMS to manage our main websites but with SharePoint we no longer have to rely on one or two key employees to post the work that many have done. We also now have a central location for all of these files to be viewed and posted once they are made …
In order to unify all our locations and corporate offices to one platform we went with Google products and eliminated MS SharePoint. This was an executive decision that I had no involvement in.
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
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.
SharePoint Document Management excels as a central repository for storing, organising, and retrieving documents. It supports version control, metadata tagging, secure access, and integration with tools like Power Automate. At our organisation, it's used for managing contracts, policies, and supplier documents. SharePoint Workflow Automation integrates with Power Automate to streamline approvals, gather feedback, and automate recurring tasks. This reduces reliance on email chains and manual trackers.
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.
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
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.
Windows Explorer users have some difficulty having to constantly UPLOAD / DOWNLOAD files. Specifically on the DOWNLOAD when they are used to Drag & Drop in & out of LOCAL folders via Window's explorer.
Microsoft SharePoint supports multiple "library" types. When implementing our "image" library the search function is done via "tags" and boolean logic. This is challenging to most end users. I'd like our users to be able to search our Microsoft SharePoint image library without having to enter KEYWORD or other BOOLEAN logic.
Microsoft SharePoint can also be an internal website for each department or company wide communication tool but I believe these features are geared for much larger organizations. Since we are a SMB we really aren't using these features. So maybe something more useful to SMBs would be nice.
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
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's integral to our business. It's already included with most of the Office 365 licensing we buy, so the cost is effectively zero. It stores our files, it is the foundation for custom applications, and Microsoft only continues to enhance its functionality and its connections to other Microsoft tools. SharePoint just keeps getting better and better.
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
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.
No usability issues reported. Individual teams also have allocated areas which replace legacy shared drives on local LANs. Access to Sharepoint resources is fully integrated with corporate Active Directory with additional two-factor authentication required for administrative users. Users have access to Microsoft Services Hub which allows you to create, manage, and track support requests while staying current on Microsoft technologies with access to select self-paced learning paths
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
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!
The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.
I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.
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.
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
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.
The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the content and better indexing and searching capabilities.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
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.
