My line on acronyms is fairly clear, I think that introducing acronyms by expanding them on first-use is a useful guideline and principle to try to stick by.
I'd also err on the side of generally assuming that most people, even in a technical forum, don't know all acronyms unless they're very widely known outside of the topic at hand. I don't think AOS vs SOA comes anywhere close to that line.
Some acronyms are of course better understood by their acronym, I wouldn't introduce a Local Area Network (LAN), or Domain Name Resolution (DNS), so like all guidelines there's judgement to be made.
Even then, if I were writing an intro to DNS, then I would call it an Introduction to Domain Name Resolution (DNS), because it is specifically targeted as an introduction. I wouldn't do the same for SQL, because no-one calls it Structured Query Language. Fairly often it would be more confusing if they did expand it, because quite often when people talk about SQL they're not really talking about the language at all, but using it as a short-hand for talking about SQL-compatible databases, or more specifically talking about relational database management systems (RDBMS), but "SQL" is a useful shorthand to contrast to "No-SQL" databases that were popularised a decade or two ago.