Google 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.

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.

We primarily use the solution to assist our clients. One of our clients, for example, wanted their web application to be integrated.

The ability to measure access using the solution is quite helpful. It's very helpful, in particular, for clients.

The app provides ready-made services that we can talk to without issue.

We are looking for a more robust solution that allows seamless integration.

The initial setup was quite complex.

The solution needs some features. There a lot of new requirements, like seamless integration and real-time batch updates, that we would want that should be added in future releases.

We've only used the solution for a very short time. It's only been a few months.

The app is reliable. It's very stable. We haven't had issues with things like bugs or glitches. It hasn't crashed. It's been good.

The solution is quite scalable, as it is on the cloud. It is easy for a company to ramp up as needed.

We've never had to contact technical support. Everything we've needed in terms of answering queries or finding assistance is available online.

The initial setup is not straightforward. It was complex. We are expecting it to be more seamless.

The coding turned out to be quite difficult. We had to put the legacy EPAs in place. The access was hard to deal with. Networking restrictions, etc. were also causing us problems. There was a combination of implementation issues our organization had to deal with.

In the end, deployment took three weeks. 

We had our own team at our company that was able to deploy and maintain the solution.

We were a Google partner in the past, but we aren't anymore.

I would recommend the solution. I'd rate it seven out of ten overall. If the solution offered more features, we would rank it higher.

We use the solution for clustering data. You can share the link with the current person or can provide access to someone else.

The solution is easy to use.

There should be more optimization options.

I have been using Google Cloud from my university. We are using the latest version of the solution.

I rate the solution’s stability a nine out of ten.

Seventy users are using this solution. We have plans to increase the usage depending on the upcoming projects.

The initial setup is straightforward.

The deployment was done in-house.

The solution has an on-time cost.

Around two to four persons with knowledge and professional skills are required for maintenance.

I recommend the solution.

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

We use GCP for many resources, including Google Kubernetes cluster (GK), monitoring with Stackdriver and Work Explorer, Cloud Insight, Cloud Storage for backup, Container Registry, VPC, complete VM, Memory Store, and Redis. We also use Robitankyo and the message query.

For me, the most valuable feature is JKS and Kubernetes Cluster on managed service. Moreover, the latest versions of the managed Kubernetes clusters are good. 

There is room for improvement. For instance, we encountered some issues with a potential cluster on GCP last month. Although we use GCP for all our resources, we experienced some difficulties. So, I think this aspect needs to be addressed and improved upon. And from what I can tell, GCP is working on addressing this issue.

I have been using this solution for two years. 

I would rate the stability a seven out of ten. 

I would rate the scalability of the solution an eight out of ten. 

We used global IT for the support. 

Overall, I would rate the solution an eight out of ten. 

 I'm working with GCP, managing approximately 15 GCP clusters on Kubernetes. I have strong experience with Google Cloud and am a solution architect on AWS.