Domo is a full self-service business intelligence software that combines several data analysis and reporting tools into one platform. It helps users connect to multiple data sources, create robust visual reports, manage their data, send messages in real-time, manage projects, and develop new apps.
N/A
Google App Engine
Score 8.2 out of 10
N/A
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
Pricing
Domo
Google App Engine
Microsoft Azure
Editions & Modules
No answers on this topic
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
Offerings
Pricing Offerings
Domo
Google App Engine
Microsoft Azure
Free Trial
Yes
No
Yes
Free/Freemium Version
No
Yes
Yes
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.
More Pricing Information
Community Pulse
Domo
Google App Engine
Microsoft Azure
Considered Multiple Products
Domo
Verified User
Consultant
Chose Domo
Domo is more suited for creating visualizations for executives, and usually they tend to be high level data visualizations. In this sense, it is not the most powerful tools for deep dive analysis, but it is intuitive and fast. Especially if your end users will access your …
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.
I believe that companies that record large amounts of data about their product, service employers KPIs, etc, can make the best out of Domo for reporting and data analysis, but if a company handles little data and is not recording this consistently, it will not be of much use.
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.
Exceptional Transform area of the platform - any/all raw data can be manipulated and combined to create datasources that are very useful for our departments.
Visualization layer is clean and is very business presentable. Its simple but includes depth. Visuals can be created/used by all roles throughout our firm, its not limited to analysts.
Ability to communicate and talk about insights in the data - the communication tool is exceptional. I can @ mention specific users to bring attention to a discovery. I can start a private chat. I can annotate and communicate what I am seeing. I love it.
Mobile experience is excellent. When I am on the road i can actively monitor and engage with my team due to my Domo dashboard on my mobile device. Its amazing to run the business and not worry while away from the office.
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.
Copying Reports - In Excel or Google Sheets, I like to make copies of similar reports and modify them as necessary for users. In Domo, makes copies of reports (called cards) but all copies are connected. So if you adjust the copy, it changes the original. This means a user has to recreate the report from scratch and then adjust it.
Unforgiving SQL - Domo does allow users to write their own SQL codes, which is great. However, Domo's SQL code is pickier than the other SQL database I've used (Metabase).
Text Alerts - Domo's alerts aren't always the smartest. Some of my dashboards are about the sales teams monthly performance and I get notified when there is a change of more than 20%. I always get notified at the start of the month that reports have changed from 'x' number to zero. This is expected because it's a monthly report and I hate getting texts about it. The only reason I don't term them off so I can be aware if something breaks in the middle of the month.
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.
Domo is a great up-and-coming product. There are many fantastic features that are extremely compelling to our end users, which makes Domo a great fit for our organization. As with many BI tools, there are items on the wish list that could make implementation, administration and usage easier, but I believe these will be addressed over time as the product matures and evolves. The overall concept and approach of this solution has definitely raised the bar in this area of expertise and I would like to see things advance in giving the enterprise tools that will make decision making easier and more robust in the future.
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.
The built-in user support and intuitive design of Domo makes it simple to learn and use. I find I can spend hours drilling deep, or else quickly gain an overview in just a few minutes. This is a great advantage since the flexibility fits well with the demands of my role. I enjoy using Domo since I know it will give me comparative data across almost every variable I might want to explore - I look forward to it!
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.
Pretty responsive. It took a while to get a response in selecting data points for our particular cards. Might have taken about a month? I am not sure if this was something on our end or Domo's end. But haven't had any other issues yet that required additional support from Domo.
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!
It is a true web-based application so implementation is much easier and smoother compared to other non-web based BI solutions. Also, they offered consulting services during the implementation process, which was helpful. Also, they provided lots of on-demand training courses and videos, which I liked.
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.
At the end of the day, end-user adoption and taking the burden of IT to build reports was my goal. Demoing and testing many BI tools, DOMO is the one that allowed both to happen.
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.
I mentioned a "previously un-analyzable" dataset that we were able to visualize in Domo - the result was business re-alignment for increased productivity, cost savings and ROI.
It's tough to quantify the ability to provide insights that have been desired for years but not possible - we continue to amaze our executives and product managers with the analysis we can provide.
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.
