What is our primary use case?
We primarily use it as an enterprise-level firewall.
What is most valuable?
I have to incorporate my particular data, schema into Axon. I can do it in two to three ways. Either I have to do a bulk upload feature in Axon, and I have to create an Excel sheet and I have to incorporate all the columns, all the attributes, all the asset columns, and their definitions, and everything into the Excel sheet and then I have to upload it. That is a manual process, and an SME has to be required to accomplish that feature.
The feature of auto-onboarding of the assets, enterprise assets via EDC is good. EDC will scan the data within the technical metadata, and then you can associate that technical metadata, and then Axon can consume that technical metadata and associate the business metadata to that technical metadata. Following some Axon systems, we have to create some systems to associate that technical metadata, as there has to be some logical hierarchy that has to be followed. It allows for some flexibility. You can have related features like policies, business glossaries, or maybe some regulatory compliance feature policies, et cetera, as well as governance.
What needs improvement?
If you have a DQ rule, data quality rule, on any particular subject area or any particular column, then one cannot create directly a rule in Axon. It has to ingest the technical tool we create in IDQ then into the Axon.
Informatica Axon itself is not a very complete tool. It's highly dependent on Enterprise Data Catalog and IDQ. Blending data catalog and IDQ makes it complete. When I say blending, I mean in the sense they have internal plugins, internal listeners. Axon has internal listeners for reading EDC, as well as IDQ components. EDC is Enterprise Data Catalog, which's a metadata catalog from Informatica.
I would like to have broader connectivity. Axon currently is limited. It cannot connect to any other application. It does not have any connectors for other applications. I want more applications to have connectivity to Axon. Axon should create more plugins for connecting to other applications, which are currently dominating the market.
The solution still is a bit manual in its functionality. We want t to be more automation-driven.
The solution needs to be more resilient.
For how long have I used the solution?
I've been working with the solution for the last three years.
What do I think about the stability of the solution?
Currently, what happens in a week or two, the server goes for a toss because Axon still uses PostgreSQL as its database. They have all the services and they, basically, fetch all the backend tables. All the tables are in the PostgreSQL database. That is also a kind of constraint for Axon as PostgreSQL nowadays is a solution that no one uses. That's why the server always goes for a toss and we have to restart the server. They have to make it more resilient. The resilience is missing.
For example, in EDC they have multiple nodes. When one node goes down, you can still use the backup node. You have to just configure it. In Axon, this does not work like that. They have to make it more vigilant instead of having to restart the cycle and again restart all the services, pre-configured services to get it up and running. That thing is a bit scary sometimes as, over in product staging and dev, it works, however, for production, if it goes down and we need our scanning and some processes running, then it's pretty tough.
How are customer service and technical support?
Technical support, nowadays, is a bit of a let-down. They will reply once you raise a ticket. They normally categorize their ticket as a P1, P2, or P3. A P1 ticket is for production for the first failure and the P2 and P3 are for normal failures. They reply promptly, however, the response is not very good. Earlier, GCS, Global customer support used to make sense and be helpful. However, nowadays, their quality of service is really going down. The person that comes to attend the ticket is often not very equipped, or not technically not very capable.
Therefore, you need to have a regular follow-up. Normally what they do is not solve the problem. They will ask you, source this, the source that, and then send some kind of justification instead of trying to solve the issue. Sometimes the client is not technically equipped to answer their ticket. They want to see some logs which get embedded. They ask businesses for those logs. Then, the business has to log into Unix, find a particular folder, and access that backlog. These become a challenge for our business as there are not that many Unix-friendly people. In any case, it lengthens the process and draws out the resolution..
What other advice do I have?
When I started, I was using version 6.3 and now it's 7.2.
The solution is on-prem in the sense that it's a web browser. It's browser-based so that you can use it on your desktop for unblocking your firewall. It's an enterprise firewall, you can deploy it. Since it's browser-based, it does not matter where the server is. The server can be on-prem and it can be deployed on an iPaaS service or other infrastructure at your service.
Informatica has created the Axon brand in such a way that it's kind of an interesting strategy for them. Once you have Axon you cannot buy it as a standalone product. You will always have to buy IDQ and EDC. That's a sales strategy. However, they really need to improve on their customer support. I really would advise Informatica to work on support. They really need to catch up on this, and they really need to add more qualified engineers to their customer support team to meet the client's expectations.
Overall, I would rate the solution at a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner