uuid: - value: 05232b81-d945-4112-99bf-d1adb2552428 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:12+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Why is everyone moving to SQLite?' created: - value: '2024-05-28T00:00:00+00:00' changed: - value: '2025-05-11T09:00:12+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/05/28/why-is-everyone-moving-to-sqlite langcode: en body: - value: |
I've noticed a lot of Developers recently adopting SQLite for their database and I wonder why this is.
Laravel changed their default database to SQLite for local development.
It simplifies the development environment as there's no need for a separate database like MySQL or MariaDB but, if you'll be using one of those in production, won't that cause more issues when you migrate your local application?
Drupal supports using SQLite, but, other than for my automated testing course, or when running automated tests, I've always used a MySQL or MariaDB database.
Maybe this is something to keep an eye on and potentially use more for some scenarios in the future.
format: full_html processed: |I've noticed a lot of Developers recently adopting SQLite for their database and I wonder why this is.
Laravel changed their default database to SQLite for local development.
It simplifies the development environment as there's no need for a separate database like MySQL or MariaDB but, if you'll be using one of those in production, won't that cause more issues when you migrate your local application?
Drupal supports using SQLite, but, other than for my automated testing course, or when running automated tests, I've always used a MySQL or MariaDB database.
Maybe this is something to keep an eye on and potentially use more for some scenarios in the future.
summary: null field_daily_email_cta: { }