Arqora Notes

Technical notes, decisions, experiments, and updates from Arqora.

A maintained record of how Arqora studies systems, makes technical decisions, documents experiments, and turns internal work into public software over time.

5 published notes

Why Arqora moved to PostgreSQL

A technical note on choosing PostgreSQL for Arqora CMP, support workflows, and long-term relational data.

Quick summary
01

Arqora CMP depends on relational data such as tickets, messages, users, routing rules, and audit trails.

02

PostgreSQL gives the project reliable structure without locking the system into a narrow product shape.

03

The decision keeps the platform easier to reason about as workflows become more complex.

Choosing simple infrastructure before scale

A decision note on keeping Arqora infrastructure simple while the project is still forming its core systems.

Quick summary
01

Arqora does not need heavy infrastructure before the product surface and workflows are clear.

02

Simple hosting, generated pages, and managed services reduce operational load at the early stage.

03

The system can still be designed with future migration paths in mind.

Building with public technical notes

Why Arqora uses notes to document decisions, experiments, and technical direction as the system changes.

Quick summary
01

Notes give Arqora a simple way to explain technical changes without turning every update into marketing content.

02

They help future readers understand the reasoning behind architecture and interface decisions.

03

The notes system also makes the site more useful for crawlers and humans at the same time.