
The Application Team's self service capability through the API is incredibly useful for the our Application Team. One example of this is the Slackbot we developed that lets application owners ask, can my new application communicate with the database? and in response to that question, the API will provide an immediate validated path analysis.
By providing this level of visibility into the network, it reduces the amount of time spent on lower level connectivity allowing my core network team to spend more time on designing the overall structure. Review collected by and hosted on G2.com.
The way NQE is setup is a major bump in the road due to its proprietary syntax, it is an amazing piece of technology, no doubt, but forcing our dev team that develops only in Go and Python to learn a new query language just to interact with this feature increases our workload and causes additional work for us. To further compound the problem, we have to spend developer time writing wrapper libraries to make the NQE usable by the rest of the engineering team. Review collected by and hosted on G2.com.