Need advice about which tool to choose?Ask the StackShare community!
Liquibase vs MariaDB: What are the differences?
Data Definition Language (DDL) Support: Liquibase offers comprehensive support for managing database changes, including creating, altering, and dropping database objects like tables, views, and indexes, while MariaDB, being a specific relational database management system, focuses on executing SQL statements related to DDL like creating and altering tables.
Version Control Capability: Liquibase excels in version control management, allowing developers to track, manage, and apply database changes incrementally using changesets. On the other hand, MariaDB lacks built-in version control features and relies on external tools or manual processes for versioning database schemas.
Cross-Database Platform Support: Liquibase provides support for multiple database platforms, enabling developers to apply the same changeset across different databases like MySQL, PostgreSQL, Oracle, and more. In contrast, MariaDB is designed primarily for MySQL compatibility, meaning it might not seamlessly function across diverse database systems without modifications.
Rollback Functionality: Liquibase offers a robust rollback mechanism, allowing users to undo specific changesets or an entire update, ensuring data integrity and consistency in case of errors. MariaDB, while supporting some rollback capabilities, may not provide the same level of granularity and flexibility as Liquibase.
Automation and Scripting: Liquibase enables automation of database changes utilizing scripts, making it easier to deploy changes consistently across multiple environments. MariaDB, while supporting scripting through SQL or other tools, may require additional manual processes or configurations for automating database modifications efficiently.
Schema Evolution Handling: Liquibase simplifies schema evolution by autogenerating SQL scripts to migrate the database schema from one version to another, promoting agile development practices. In contrast, MariaDB users may need to manually write migration scripts or use third-party tools to manage schema evolution effectively.
In Summary, the key differences between Liquibase and MariaDB lie in their support for DDL operations, version control capabilities, cross-database platform compatibility, rollback functionality, automation of database changes, and handling schema evolution.
Hi all. I am an informatics student, and I need to realise a simple website for my friend. I am planning to realise the website using Node.js and Mongoose, since I have already done a project using these technologies. I also know SQL, and I have used PostgreSQL and MySQL previously.
The website will show a possible travel destination and local transportation. The database is used to store information about traveling, so only admin will manage the content (especially photos). While clients will see the content uploaded by the admin. I am planning to use Mongoose because it is very simple and efficient for this project. Please give me your opinion about this choice.
The use case you are describing would benefit from a self-hosted headless CMS like contentful. You can also go for Strapi with a database of your choice but here you would have to host Strapi and the underlying database (if not using SQLite) yourself. If you want to use Strapi, you can ease your work by using something like PlanetSCaleDB as the backing database for Strapi.
Your requirements seem nothing special. on the other hand, MongoDB is commonly used with Node. you could use Mongo without defining a Schema, does it give you any benefits? Also, note that development speed matters. In most cases RDBMS are the best choice, Learn and use Postgres for life!
MongoDB and Mongoose are commonly used with Node.js and the use case doesn't seem to be requiring any special considerations as of now. However using MongoDB now will allow you to easily expand and modify your use case in future.
If not MongoDB, then my second choice will be PostgreSQL. It's a generic purpose database with jsonb support (if you need it) and lots of resources online. Nobody was fired for choosing PostgreSQL.
Any database will be a great choice for your app, which is less of a technical challenge and more about great content. Go for it, the geographical search features maybe be actually handy for you.
SQL is not so good at query lat long out of the box. you might need to use additional tools for that like UTM coordinates or Uber's H3.
If you use mongoDB, it support 2d coordinate query out of the box.
Any database engine should work well but I vote for Postgres because of PostGIS extension that may be handy for travel related site. There's nothing special about your requirements.
Hi, Maxim! Most likely, the site is almost ready. But we would like to share our development with you. https://falcon.web-automation.ru/ This is a constructor for web application. With it, you can create almost any site with different roles which have different levels of access to information and different functionality. The platform is managed via sql. knowing sql, you will be able to change the business logic as necessary and during further project maintenance. We will be glad to hear your feedback about the platform.
We actually use both Mongo and SQL databases in production. Mongo excels in both speed and developer friendliness when it comes to geospatial data and queries on the geospatial data, but we also like ACID compliance hence most of our other data (except on-site logs) are stored in a SQL Database (MariaDB for now)
Pros of Liquibase
- Great database tool18
- Many DBs supported18
- Easy setup12
- Database independent migration scripts8
- Unique open source tool5
- Database version controller5
- Precondition checking2
- Supports NoSQL and Graph DBs2
Pros of MariaDB
- Drop-in mysql replacement149
- Great performance100
- Open source74
- Free55
- Easy setup44
- Easy and fast15
- Lead developer is "monty" widenius the founder of mysql14
- Also an aws rds service6
- Learning curve easy4
- Consistent and robust4
- Native JSON Support / Dynamic Columns2
- Real Multi Threaded queries on a table/db1
Sign up to add or upvote prosMake informed product decisions
Cons of Liquibase
- Documentation is disorganized5
- No vendor specifics in XML format - needs workarounds5
