Skip to content

Limitations

David Ciulla edited this page Nov 7, 2026 · 2 revisions

Limitations

Introduction

Laravex is a faithful Elixir port of the Laravel developer experience, but it is not a full reimplementation of every Laravel subsystem. The configuration files mirror Laravel's structure so that moving from one to the other is familiar, but the underlying driver implementations cover only portable, zero-Hex-dependency options.

This page reflects the current source. Every "Supported" assertion is verified against lib/laravex/ — not aspirational. Unsupported drivers raise ArgumentError at runtime if configured, with a clear message pointing to the supported alternatives.


Database

The database layer shells out to the CLI tool for each adapter (no Ecto, no Hex database drivers). The connection module is Laravex.Database.Connection.

Driver / Connection Status Notes
SQLite ✅ Supported Via sqlite3 CLI on PATH; DB_CONNECTION=sqlite (default)
MySQL / MariaDB ✅ Supported Via mysql CLI on PATH; DB_CONNECTION=mysql or mariadb
PostgreSQL ✅ Supported Via psql CLI on PATH; DB_CONNECTION=pgsql or postgres
SQL Server ❌ Not implemented Config key exists; raises if used

Remaining limitations:

  • No connection pooling. Every query spawns a new CLI process — not suitable for high-concurrency workloads. Consider connection pooling at the reverse proxy or load balancer level.
  • SQLite-biased Blueprint types. Column type macros (string, boolean, timestamp, etc.) emit SQLite-friendly SQL (TEXT, INTEGER). MySQL- and PostgreSQL-native types (e.g. JSONB, ENUM, TINYINT) must be declared with Blueprint.add(bp, raw_sql).
  • Limited schema introspection. has_table? / has_column? / has_index? use SQLite's sqlite_master; MySQL and PostgreSQL introspect with equivalent queries, but column info is string-keyed and may differ across adapters.

Cache

Cache is managed by Laravex.Cache.Manager.

Driver Status Env var
array ✅ Supported CACHE_STORE=array
file ✅ Supported CACHE_STORE=file
database ✅ Supported CACHE_STORE=database
redis ✅ Supported CACHE_STORE=redis
Memcached ❌ Not implemented No Memcached client
DynamoDB ❌ Not implemented No AWS SDK
Octane ❌ Not available No Octane equivalent

Default: CACHE_STORE=database (falls back to array if the cache table is missing).

Remaining Redis limitations: plain TCP via :gen_tcp only (no TLS, no Redis Cluster / Sentinel, no connection pooling). AUTH is sent when database.redis.*.password (or REDIS_PASSWORD) is set.


Session

Sessions are managed by Laravex.Session.Store.

Driver Status Env var
file ✅ Supported SESSION_DRIVER=file
database ✅ Supported SESSION_DRIVER=database
redis ✅ Supported SESSION_DRIVER=redis
cookie ❌ Not implemented —
DynamoDB ❌ Not implemented No AWS SDK

Default: SESSION_DRIVER=database. Sessions expire after SESSION_LIFETIME minutes (default 120). Garbage collection runs probabilistically (session.lottery = [2, 100]).

Remaining Redis limitations: same as Cache — no TLS, no Cluster, no password auth over the wire.


Mail

Mail is handled by Laravex.Mail.Mailer.

Driver Status Env var
log ✅ Supported MAIL_MAILER=log — writes to the application log
array ✅ Supported MAIL_MAILER=array — for testing; accessible via Mailer.sent/0
smtp ✅ Supported MAIL_MAILER=smtp — zero-dep SMTP via :gen_tcp / :ssl
AWS SES ❌ Not implemented No AWS SDK
Postmark ❌ Not implemented No HTTP client driver
Resend ❌ Not implemented No HTTP client driver
Sendmail ❌ Not implemented No sendmail wrapper

Default: MAIL_MAILER=log. To test mail without sending, call Laravex.Mail.Mailer.fake/0 and assert with Laravex.Mail.Mailer.assert_sent/1.

Remaining SMTP limitations: AUTH LOGIN mechanism only (no PLAIN, no XOAUTH2). No connection reuse — a new TCP connection is opened per message. No inline attachment encoding.


File Storage

Storage is handled by Laravex.Filesystem.Storage.

Driver Status Env var
local ✅ Supported FILESYSTEM_DISK=local
s3 ✅ Supported FILESYSTEM_DISK=s3; also works with S3-compatible services (MinIO, R2)
FTP / SFTP ❌ Not available —

Default: FILESYSTEM_DISK=local.

Remaining S3 limitations:

  • Bodies are loaded into memory in full (no streaming).
  • No automatic retry on transient network errors.
  • No multi-part upload support.
  • stream_download is local-only; it falls back to a full read on S3 disks.
  • TLS validation uses OTP's default :httpc behaviour (no custom CA bundle).

Queue

Jobs are dispatched through Laravex.Queue.Worker.

Driver Status Env var
sync ✅ Supported QUEUE_CONNECTION=sync — runs job immediately in-process
database ✅ Supported QUEUE_CONNECTION=database — persists to jobs table
deferred ✅ Supported QUEUE_CONNECTION=deferred — in-memory ETS, processed asynchronously
redis ✅ Supported QUEUE_CONNECTION=redis — RESP LPUSH/BRPOP via :gen_tcp
AWS SQS ❌ Not implemented No AWS SDK
Beanstalkd ❌ Not implemented No Beanstalkd client

Default: QUEUE_CONNECTION=database.

Remaining Redis limitations: same as Cache — no TLS, no Cluster, no password auth.


Broadcasting

Events are broadcast via Laravex.Broadcasting.Broadcaster.

Driver Status Env var
log ✅ Supported BROADCAST_CONNECTION=log
null ✅ Supported BROADCAST_CONNECTION=null
array ✅ Supported BROADCAST_CONNECTION=array — for testing
pubsub ✅ Supported BROADCAST_CONNECTION=pubsub — in-process Registry fan-out
Reverb ❌ Not implemented No WebSocket server
Pusher ⚠️ Stub only Config scaffold exists; no live Pusher client
Ably ❌ Not implemented No Ably client

Remaining pubsub limitation: in-process only. Registry.dispatch delivers to PIDs within the same BEAM node — messages are not relayed across cluster nodes or to browser clients. Use Pusher or Ably for real-time WebSocket delivery to end users.


Logging

Logging is handled by Laravex.Log.Logger.

Driver Status
single ✅ Supported — single log file
daily ✅ Supported — date-rotated files
monthly ✅ Supported — month-rotated files
stderr ✅ Supported — writes to standard error
errorlog ✅ Supported — Erlang error logger
null ✅ Supported — discards all output
Slack ❌ Not implemented
Syslog ❌ Not implemented
Papertrail / Logtail ❌ Not available

Notifications

Notifications are sent via Laravex.Notifications.Notifier.

Channel Status
mail ✅ Via Laravex.Mail.Mailer (log / array / smtp)
database ✅ Stored in notifications table
log ✅ Written to application log
broadcast ✅ Via Laravex.Broadcasting.Broadcaster (log / null / array / pubsub)
Slack ❌ Not implemented
Vonage (SMS) ❌ Not implemented

Other Unsupported Features

Feature Status Notes
Redis (cache/session/queue) ✅ Supported RESP over :gen_tcp; see Cache / Session / Queues above
WebSockets / Reverb ❌ Not available No Reverb/Pusher protocol; use pubsub for in-process fan-out only
Horizon ❌ Not available No Laravel Horizon equivalent
Telescope ❌ Not available No debug assistant
Octane / Nova / Passport / Scout / Socialite ❌ Not available Out of scope for now
Deferred provider loading ❌ Not implemented All providers boot eagerly at startup
SQL Server ❌ Not implemented Config key exists; raises if used
Multi-tenancy / multi-DB ❌ Not available Single default connection at a time
Rate limiting ⚠️ Cache-backed Uses the configured cache store (including Redis when selected)

Summary

If you need any of the unsupported drivers, you have three options:

  1. Implement a driver — most subsystems are small GenServers with a clear @supported_drivers guard. Adding a new driver means extending handle_call/3 and updating the guard.
  2. Use an external service — call a third-party API directly from your application code.
  3. Migrate to full Laravel — Laravex's config structure mirrors Laravel's, so moving configuration values is straightforward.

See Deployment for guidance on running Laravex in production within these constraints.

Clone this wiki locally