> Kong comes with its own RESTful Admin APIs. It is built on top of OpenResty (an extension of NGINX) and LuaJIT. These provide access to all kinds of configura

> Kong comes with its own RESTful Admin APIs. It is built on top of OpenResty (an extension of NGINX) and LuaJIT. These provide access to all kinds of configurations that can be made available. We have done another addition on top of it by adding the Konga dashboard to manage Kong via a GUI. So, this is not a brand-new product, this is a fancy dashboard/configuration builder for OpenResty. And it looks like the focus is on interactive service building, with configuration stored in database, seemingly without configuration review or change logging (I could not find those in manual at least). This seems like a dangerous practice for production systems which can easily lead to data loss or outages if someone mis-types some routes somewhere. I found configuration-as-a-code systems to be much nicer than random dashboards, at least for production use. Yes, it is a bit harder to set up initially, but you never have to worry about "hey! why was it working yesterday and not today?". (The manual does describe "db-less" deployment, but it seems like an afterthought and definitely not the main focus...)