What do you like best about Aiven for PostgreSQL?
Everything that we deploy works flawlessly so far, but our deployment of choice is terraform and Aiven's terraform provider is quite immature, and poorly documented. This causes problems for us which Aiven have done good work to address some of, but still have some way to go
I like that it has write ahead logging, which cloudSQL doesn't have for cloudSQL postgres, Aiven are more up to date in this regard. Review collected by and hosted on G2.com.
What do you dislike about Aiven for PostgreSQL?
your terraform documentation! plus your provider doesn't/didn't work as terraform providers should, violating basic assumptions of the terraform framework and causing me weeks of work when it should have been hours. The software felt untested, and this caused us a couple of weeks to sort out (which, to Aiven's credit, we did sort out)
Please see a list of terraform providers that manage to keep up to date enough that they can submit their documentation to the official terraform website https://www.terraform.io/docs/providers/index.html (that's 133 providers). IMO this is an absolute minimum if you're going to be releasing a terraform provider for an expensive paid for product.
This has totally coloured my view of Aiven because your service seems to be working flawlessly and it seems to have unjustly turned me off what seems to be an otherwise excellent product. Logging into the console is a genuinely pleasant experience but it is not a solution to a problem inside terraform - If it's not in terraform it makes it very difficult to interface with our automation.
Additionally, your Aiven_project_service resource is totally overloaded, I get that they probably share a parent object but I think they should be separate resources, When I'm configuring Postgres I don't want to also have to wade through the documentation on elastic cloud, kafka etc as well, this is compounded by the already lacking documentation, which forced me to manually inspect attributes of resources on runs.
Please forget the CEO's/CTO's you're showing your web console, and instead consider the people that will actually be using your software. The business (hopefully) doesn't run because they have sys admins clicking through a UI!
I'm sure your infra is as (declarative) code, there's of course very good reason for it; I want mine to be as well. Review collected by and hosted on G2.com.
