At our work, we deploy services, especially for payments, and get feedback on the integrated percentage of these deployments. These services are scattered across different locations, so I also handle administrative tasks, integrating AI for subscription management and addressing globalization concerns. We're focused on securing our operational environment and streamlining account management. There seem to be some challenges in the process, and I utilize Looker for analysis and resolution.
Recently, I've found more value in what I'm currently exploring. It's quite effortless to navigate through various applications and review their updated data in real-time. While using Looker, I encountered a hitch in the application setup process; it took a bit of time and effort to configure, but once it was up and running, the results were remarkably impressive.
Stability needs improvement.
I have been using Looker for the last four years.
My experience over the past six and a half months has been quite intense. The challenges I faced were with Looker, which was crucial for the app we were developing. Initially, there were some issues in setting it up, and without resolving these, we wouldn't have been able to proceed. It was necessary to break down and address these hurdles to move forward.
I would rate the scalability an eight and a half out of ten.
I've only had a single encounter with it. The folks handling it did respond. I assured them that I hadn't faced many challenges. If I did encounter any, I'd go back and check.
The accessibility concerns are significant. We have approximately forty-five users, which makes the cost of licensing quite expensive. This aspect holds paramount importance for us. There are some specific reports we need to share. We use Power Desktop within our domain and intend to explore other options. That's why we use Looker—it provides easier and seamless access for individuals outside the licensing sphere.
Our data usage is in Google, using SQL. However, the dataset size varies significantly. While some sets are not extensive, others fall into the category of large enterprise-level data, impacting costs. It's not a singular size; it varies. We're considering transitioning to Looker due to performance issues, specifically in this context.
I would rate the solution an eight. We have various pros and cons to consider. Right now, the key advantage is the easy access and availability. Sharing information is seamless, and it facilitates quick comparisons with near-immediate updates—it's almost live. We don't need instances for file logs; reports are accessible right there. Visualizing data is also straightforward. In terms of drawbacks, the experience is similar to Looker, functioning as an IPaaS.
