[goodpoint]

Familiarity supports popular language runtimes, tools, and idiomatic APIs experience deploying this technology to production today

Stability follows a predictable release and versioning scheme (note: NOT frequent is fine and in some ways more desirable. security patches are always welcome of course.) biases for non-breaking changes easing long term maintainability publishes a regular changelog open-source and/or open-source backed service ideally public governance: roadmap, issue tracking, and decision making all visible

Reliability can be trusted to work as expected; ideally does one thing well social proofs exist (careful!)

Well understood limits, and trade-offs accessible docs objective benchmarks and/or published service quotas friendly community (Code of Conduct, blogs, chats, podcasts, etc.)