Google Cloud Platform Cloud Identity-Aware Proxy Reviews

Our financial system is on Oracle-based, SaaS, hosted on the Oracle cloud. From different XML sources, we had to bring in high volumes of transactions into the financial system.

Before we put all of the data into the product and financial system, we need the data to go through some data messaging, and create some rules and derive some values. There are five or six million records every day.

Google has some very good tools on its platform. They have an App Engine and cluster-based programming so that you are able to achieve high performance. 

Because this is a multiple source system, we need a centralized place where all of the data rules are maintained and where all of the data transformations are performed.

Being from an Oracle background, Oracle doesn't have the tools that Google has to transform the high volume data.

It can perform that validation for the high volume transactions in less time, it can be transformed in minutes.

I like this solution. It has a lot of abilities such as data processing and cluster data creation.

The way they use the sources efficiently and the performance are good. The cost is also less, depending on the way that you code.

There is a lot of flexibility and a lot of control if you use this efficiently.

I would like to see the drag and drop features improved. They have a lot of hand-coded coding. Now they are doing less coding and more drag and drop and configuration. 

From a developer's perspective, it would make it simpler and also the less manual coding will lead to fewer defects. Less coding ability but most coding should be automated using a drag and drop functionality.

The setup could be more user-friendly.

In the next release, I would like to see improved drag and drop features, less coding abilities, or zero coding abilities. This would mean that you can do it by using your configurations, or even when you drag and drop it can be an orchestration so that anyone can do it. It would not be just some hand-coded kind of development that will be used by developers in the future.

We are typically a solution provider and we implemented this solution twelve months ago.

It's a stable product.

The scalability is really good.

There are not many end-users who come in and log in every day, because all of these transformations are completed automatically. From the administration standpoint, there are three or four people taking care of the databases and the application layer. The product is all automated and it's a matter of a back and forth thing.

I have not contacted Google support.

We were using Oracle. Previously, we were not using any products. Other products such as JCS and ICS are not this kind of solution. They are that capable. Oracle may have some other products, but I am not aware of it.

The initial setup was ok, although it can be made to be more user-friendly.

The length of deployment depends on the client's requirements. This particular client has very stringent requirements and it had to go through multiple QA processes. It did take some time but that had to do with the change in management.

You need three or four people with varying skillsets if you are implementing this. We had approximately five for this.

I think that the cost is metered based on the data, but I don't have the details.

This is an awesome product.

This solution is pretty automated. When you come from an administrative standpoint, they come and just do some maintenance now and then. They're very few.

My advice for anybody who is implementing this solution is that they have to be very careful. Though this has all of the capabilities, be very careful. Before they engage in the design, you have to understand the volume of transactions you are going to have. What are the turnaround times that you need and the performance considerations? Depending on that, you have to define the architecture of the solution. There are various factors.

There is a thought process before you go into the developing mode.

You have to go through many different people and understand what the restrictions of the various databases that Google has provided are. You have a lot of tools to select before you start developing. There are many tools on this platform and you have to pick the right ones for the right solution. Cost and performance on this type of solution dictate that.

A thorough analysis should be done before you get into this because it's not easy.

I would rate this solution a nine out of ten.

I use Google Cloud IAP to secure my applications by verifying user identities.

I like Google Cloud IAP because it is easy to use and stable.

As an individual developer, I would like Google Cloud IAP to offer more flexibility, especially for smaller-scale usage.

I have been using  Google Cloud IAP for seven years.

I would rate the stability as a nine out of ten.

The support is very good.

I have previously used AWS, but Google is my preferred option.

I would recommend Google Cloud IAP for those starting, especially for individuals or smaller projects. While larger enterprises might lean towards AWS, I have found Google Cloud to be effective for my needs. Overall, I would rate Google Cloud IAP as a nine out of ten.

I use the solution for emails, reminders, and other personal work. I am a service engineer, and I use the solution alone.

I like that the solution has high availability and is stable and free. Likewise, the interface is quite good.

The local sales team contact is not easily available. If I want to contact a sales account manager at Google directly to buy something, I cannot approach them directly. I have to go through layers of vendors. Only then can I somehow approach.

I've used Google Cloud Platform for about five or six years now.

I rate the solution's stability a nine out of ten because there is scope for improvement.

The initial setup was easy and intuitive. It was an easy transition.

I rate Google Cloud Platform a nine out of ten. I recommend the solution to others, and my friends and family always use it.

The solution can be used for building the infrastructure on the cloud.

The solution's security should be improved.

I have been working with Google Cloud Platform Cloud Identity-Aware Proxy for a few months.

The solution's stability seems good.

Google Cloud Platform Cloud Identity-Aware Proxy is a scalable solution.

Before Google Cloud Platform Cloud Identity, I worked with AWS and Azure. I switched to Google Cloud Platform Cloud Identity because of the client's needs.

Google Cloud Platform Cloud Identity-Aware Proxy is a cloud-based solution.

Overall, I rate the solution a seven out of ten.

We use the solution for continuous integration and deployment of applications on databases.

The solution's most valuable features are Google domains, UI setup, easy server access, and intuitive dashboards.

The solution's naming conventions feature needs improvement. We encounter issues while setting up emails as well. They should improve this particular area. Also, they should integrate the solution with more applications.

I have been using the solution for six months.

The solution's stability is good.

We have five solution users in our organization. It is expensive to scale up the solution.

The solution's initial setup was fine. However, it took a lot of work to name the features. The process involves setting up the server, connecting to the gateway, and setting up user access and security codes.

The implementation of the solution was done natively on the platform.

The solution generates a good return on investment.

We pay for the solution’s compute engine every month.

I rate the solution as an eight. I advise others to go through the documentation before deploying it. They can set up a small cluster to practice before implementing it.

I've been using Google virtual machines, Google FUSE. It has many, many products across the entire cloud platform. GCP can be used for data storage and for virtual machine creation.

It has some stack of products in it that I have found quite useful.

The solution is very easy to use. It's easy to navigate and to work with.

It's quite a flexible product.

We've found the solution to be scalable. 

The product is great. I can't think of a way it can be improved. There aren't any missing features. It's quite complete.

The solution could be more reasonably priced. We find it to be a bit expensive right now.

I've been using the solution for about a year or so. It hasn't been very long just yet.

The scalability of the solution is very good. If a company needs to expand it, it can do so with relative ease. It's not hard at all.

I'm not sure how many users in total are on it in our organization. It might be between ten to 20 people or so. There aren't too many people on it currently.

I plan to continue to use it going forward. I can't speak to the company's plans for if it, and that includes increasing usage or not.

I've never had the chance to reach out to technical support, and therefore can't speak to how helpful or responsive they are. I cannot evaluate them having had no direct interactions with them.

There isn't really an installation process for this solution. It's on the cloud. You don't need to implement anything. It's all just ready to go.

The solution could be cheaper. Right now, it's a bit expensive.

We've looked at the Oracle Cloud Platform and Amazon AWS and both services are good.

We're always using the latest version of the solution. It's always the latest as we are on the cloud deployment model and it auto-updates.

I'd rate the solution at a nine out of ten. Its capabilities have been very good overall and we've been very happy with it.

I'd recommend the solution to other users and organizations. It's worked well for us.

We use it for software social media analytics. That software can call social media like Facebook, Instagram, and news online media. We call them and put them in the container. And then we analyze the data and display it on the dashboard. We use the GCP to run our server production.

We only use what we need to put in the application to create a server. We do not need to maintain the hardware. 

I think this product needs to shift the focus from our software, our solution, like social media analytics to our customers; not maintenance in the hardware. We focus on our business for the maintenance and infrastructure to develop the software. 

I have been using this solution for two years. 

We use it to up the server like the compute engine. For the compute engine, we just put the CPU with what I need, and then storage capacity what I need, and then just click, and it runs. We don't use it yet to have integration with other platforms or systems. 

We don't get any bugs in the software.

We do have plans to increase usage when our client base increases, we will increase the capacity, like the storage and the compute. Maybe in a year or two. 

We used to contact support to handle our problems at the beginning of our implementation. We're not so experienced with the system so we need their guidance. We are satisfied with the support. We have to pay to use technical support. There are a lot of charges. We open the ticket and then have to pay for it. It shouldn't be like that. We use the infrastructure and then we pay. We just input them for the system, we do not have to pay again.

The setup is of medium complexity. It is not too difficult, it is medium level to operate GCP.

It took only two days to set up the server. The server itself took three hours. Three hours to set up the server and then the deployment. We built the system over a long time. But to deploy we set the infrastructure like the server, firewall, in the GCP. It took five hours to deploy.

We deployed it ourselves.  

I would recommend GCP. We will focus to develop our system, our product, and it's a matter of whether or not the infrastructure can handle GCP.

I would rate it an eight out of ten. 

In the next release, I would like to see a machine learning system. 

It's a cloud-based solution, so it's always the latest version. We use it for identity management, monitor resources, and to monitor the cloud resources. The number of users are small, but the number of resources being managed is large. We plan to roll it out to about 30,000 people.

There is a certain accessibility feature that I can set using a cloud identity, which is really valuable to us.

I think that the documentation could be a bit better in terms of what is presented on the screen versus what actually happens. There's a little bit of confusion under your resource discovery you get in a search bar having to do with the level of complexity of the product design. But I think the documentation could be better.

We have been using Google Cloud Platform Cloud Identity-Aware Proxy for about a year.

It is very stable.

It scales well, in fact, it's quite relevant. We've not put it to an extreme level of scale, but we use it at a medium level of scalability. It's working well.

Google's technical support is really good. In fact, I've only been in touch through email and they've been really responsive. In fact, most of our responses happen in minutes.

The setup is straightforward. I don't think it's a function of how long it takes to set up. it's a continuous deployment. At the time it was a new resource that has to be reconfigured. The initial set up was a few days, but after that its incremental changes that we do.

We've evaluated Microsoft.

I would rate Google Cloud Platform Cloud Identity-Aware Proxy at an eight out of ten.