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
Workday HCM
Score 8.2 out of 10
N/A
Workday Human Capital Management is a cloud-native system offering a globally
consistent user experience. Workday HCM is part of an intelligent, unified system with other
Workday products.
N/A
Pricing
Google App Engine
Microsoft Azure
Workday Human Capital Management
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
No answers on this topic
Offerings
Pricing Offerings
Google App Engine
Microsoft Azure
Workday HCM
Free Trial
No
Yes
No
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.
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.
I would say it's well suited in every environment because I think it does so much. It's like the holy grail of HRIS systems is what I like to call it because thinking about all parts of the employee lifecycle, it lives here in Workday Human Capital Management. So I love the fact that you can do the people data analytics, you can store employee records, the talent acquisition pieces there. I'm thinking I can't think of anything negative right now except for the fact that I can't drill down into the data for the people analytics side. Other than that, I think it's literally, yeah, the holy grail of HRIS systems, I love it and I would highly recommend it.
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.
Groups employees in management hierarchies and creates Org Charts that are easy to navigate and allow for visualizing management chains regardless of employee locations
Intuitive and easy to use. The Workday search functionality works very much like Google; one can search for anything that they have access to in the database and drill down into the various details. All information is connected through hyperlinks and users can easily keep digging into the details for as far as their security access would take them.
Tasks such as to do, review or approve items are sent to the user's Workday Inbox, very much resembling email. Notifications about outstanding "to do" items are also sent to each the user's work email address on a daily basis.
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.
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 is work to make one system the source of truth for our data, but now that it is done, there is less work involved in staying on this path. This means for us that maintaining and/or implementing new modules like performance, finance, talent, etc. is simple. It's a no-brainer
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.
Workday's on a great path in terms of user experience. Their goals is to deliver a use experience that doesn't require training or instruction, like Amazon on the consumer side for example. That's hard to do when you're talking about complex business processes and important and sensitive employee information, but they're doing it well
In 2014, Workday has changed the update process. There will be two updates a year; the updates will be delivered to customers typically in a 24 hour window during these two weekends a year. They also keep the Community up-to-date about any planned outages, etc. There is weekly scheduled downtime on Friday night.
From my perspective, the system runs like a well oiled machine and I have not had any issues with customers complaining about speed. If a report is taking long to run, the report can run in the background and you can go about your business. For larger enterprises, there is additional space and machines to process the application in what Workday refers to it as Extended Configuration Tenant
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!
Workday is still learning about the needs of higher education. I have seen rapid improvement in support and knowledge over the last year so am confident this will continue to improve. Overall however, I have found the Support Team to be extremely responsive and Workday offers the advantage of having support across several timezones so that we never wait more than a few hours for a response.
Some training is offered online. Cost is per-person. This also gets quite expensive. Training doesn’t follow a logical path A to B. Starts in middle. When you try to do it afterwards at your desk, difficult. • Training scenarios are not very real
I have done for report writing and mass imports (EIBs). They give materials and you run through examples, i.e. you don’t just watch them do tasks, so that is helpful. Training is expensive – a single reporting writing class is $600 per person for virtual training
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.
It was implemented before my joining the company. At my last company, we used Workday professional services.
Based upon my experience at my last company, I would rate the implementation experience an 8/10. There are different ways to set things up and we had different people telling us different things. It set us back a couple of times.
Regarding configuration advice, we could set things up where every manager has supervisory organizations, or have it financially based i.e. aligned to cost center/department. We chose the individual manager path and I think we should have chosen a department route. Going down the individual manager path, to maintain the information, we have to inactivate a supervisory org whenever a manager changes/leaves.
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.
Workday is an incomplete product, by this I mean it must work alongside other products and does not work by itself. Trying to make several different products work smoothly together becomes very challenging. As compared to ADP products, when purchased all together work very well all together. Also, ADP has extensive Training programs and extensive Customer Support. So ADP's products are far superior to Workday's products in my opinion.
Workday has released Financials and is continuing to develop it's Human Capital Management footprint with the addition of Workday Recruiting. I think customers will find that is easy to add on additional functionality in the system. Workday does make it easy for customers to make changes without relying on IT resources. The Business Process framework is a visual tool that allows functional resources to make changes and see the flow of the transaction
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.
Positive ROI, we were one of the first organizations that went with Workday HCM, and we received numerous discounts. Cloud systems are the way to go and we feel the system is stable for our growing work force.
The user conferences have been helpful to network and learn more deepness in the modules and functionality.
Right off the bat, our implementation costs were lower than budgeted and we had less 'billing' surprises.
