What services does A Major offer?

A Major offers web design, web app development, mobile app development (React Native, Swift, Flutter), SaaS product development, enterprise systems, UI/UX design, DevOps, performance optimization, MCP server development, AI agent infrastructure, MVP scoping, digital transformation, and engineering consultancy.

Where is A Major based?

A Major is based in Singapore and works with clients worldwide.

Do you work with international clients?

Yes. While headquartered in Singapore, A Major works with founders and businesses across Southeast Asia, Europe, and North America.

Ryu is an AI agent orchestration layer built by A Major. It enables teams to run, coordinate, and monitor AI agents at scale — connecting LLMs, tools, and workflows into reliable production systems.

Do you build MCP servers?

Yes. A Major builds Model Context Protocol (MCP) servers that connect AI agents to databases, APIs, and internal tools, enabling reliable LLM-powered workflows in production environments.

Is MariaDB a good alternative to MySQL?

MariaDB is a drop-in MySQL fork with some additional features. If you're choosing MySQL, MariaDB is worth considering — it has a more permissive licence and some storage engine improvements. It doesn't close the gap with PostgreSQL's advanced features though.

Can I migrate from MySQL to PostgreSQL?

Yes, with tooling like pgloader or custom ETL scripts. SQL syntax differences require review — stored procedures, date functions, and some data types differ. We've handled migrations of all sizes.

Which database do ORMs like Prisma and Drizzle prefer?

Both support MySQL and PostgreSQL, but their documentation, examples, and most features are Postgres-first. Enum types, JSON columns, and advanced indexing all work better with Postgres in these ORMs.

What about SQLite for small projects?

SQLite is excellent for small projects, CLI tools, and edge deployments (Cloudflare D1, Turso). For anything with concurrent writes or a multi-user backend, Postgres is the step up — not MySQL.

PostgreSQL vs MySQL ComparisonThe two giants of open-source SQL — which one should back your application

MySQL powered the LAMP stack era and still runs much of the web. PostgreSQL grew from academia and has become the preferred database for complex applications, data teams, and modern cloud-native stacks. In 2025, PostgreSQL has pulled clearly ahead in developer surveys and new project adoption. MySQL remains widespread due to sheer historical inertia — it's the default in many shared hosts, and MariaDB forks are common in enterprise environments. For greenfield projects, Postgres is almost always the better choice.

Head-to-head summary

PostgreSQL wins

Ties

MySQL wins

Detailed comparison

JSON / JSONB support

PostgreSQL

Excellent — JSONB with indexing, operators, and full query support

MySQL

Basic — JSON column exists but querying is limited

Extension ecosystem

PostgreSQL

Exceptional — pgvector, PostGIS, TimescaleDB, pg_cron, and hundreds more

MySQL

Limited — fewer extensions, less active extension ecosystem

Full-text search

PostgreSQL

Built-in and powerful — tsvector, GIN indexes, ranking

MySQL

Available but less capable — often supplemented with Elasticsearch

Write performance

PostgreSQL

Excellent — though MySQL can edge it in simple INSERT-heavy workloads

MySQL

Slightly faster for simple, high-volume INSERT workloads

Replication

PostgreSQL

Logical and streaming replication — flexible and reliable

MySQL

Mature — Group Replication and InnoDB Cluster well-tested

Licence

PostgreSQL

PostgreSQL Licence — extremely permissive, no copyleft

MySQL

GPL — commercial use in SaaS requires careful licence review

Hosted options

PostgreSQL

Supabase, Neon, Railway, RDS, Cloud SQL, AlloyDB

MySQL

PlanetScale, RDS, Cloud SQL — solid but fewer modern options

Our verdict

We recommend: PostgreSQL

PostgreSQL is the better default for new projects. Its superior JSON support, extension ecosystem (pgvector, PostGIS, TimescaleDB), full ACID compliance, and more permissive licence make it the stronger foundation. Choose MySQL if you're inheriting an existing MySQL stack, using a platform that mandates it (e.g. some shared hosts), or need PlanetScale's branching workflow.

When to choose each

Choose PostgreSQL when:

You're starting a new project — Postgres is the modern default
You need JSON storage with real querying capability (not just blob storage)
You need geospatial queries, vector search (pgvector), or time-series (TimescaleDB)
You're using Supabase, Neon, Prisma, or Drizzle — all optimised for Postgres