At the ODTUG APEXposed conference in Atlanta this week, a customer asked me to blog about how to abbreviate and pronounce the abbreviation for Oracle Application Express. I've seen numerous abbreviations (Apex, ApEx, APPEx, AppEx, APEX), and I think the lack of a formal abbreviation lends to the confusion in pronunciation. So here goes:
Whenever an abbreviation is used in informal writing, it's abbreviated in all uppercase: APEX
It's pronounced (ā'pěks). It's a long 'A' as in 'acorn'.
In formal written materials from Oracle, it is always written as 'Oracle Application Express' and never abbreviated.
In conversation and in some presentation materials, you will see the Oracle Application Express team use the above spelling and pronunciation.
----
Update on March 29, 2020: In formal, written materials, you can also use Oracle APEX.
I have dedicated a couple posts to describe who is using apex.oracle.com. I have focused on the scalability of the Application Express environment on relatively cheap hardware. And towards the end of September, we moved asktom.oracle.com to apex.oracle.com. So why not combine the best of these topics and post about who is using asktom.oracle.com?
AskTom officially moved to apex.oracle.com on 18-SEP-2009. I turned on Google Analytics a day or two later. So my snapshot of asktom.oracle.com covers the period from September 20, 2009 through November 2, 2009 - not quite a month and a half.
Some interesting statistics:
There were 517,599 "visits" and 1,005,189 page views.
78% of the page views were from hits from search engine results pages (thanks for the clarification, John Scott).
53% of the browsers are Internet Explorer - a number that I suspect gradually declines over time
People found the site searching for 'ORA-00604' more than they found it by searching for 'tom kyte'. As a shareholder of Oracle, this statistic concerns me.
The lion's share of visits comes from the United States, followed by India, United Kingdom, Germany and Canada.
All in all, though, I'm quite happy with these numbers, and how it shows that the existing hardware on apex.oracle.com and this large database (with over 10,000 workspaces/users/tablespaces) was able to absorb the additional load with no problem.
