Liquibase VS Plotter

• Version Control Integration
  Liquibase supports integration with source control systems such as Git, SVN, and Mercurial, making it easier to track changes, revert to previous versions, and collaborate with team members.
• Database Agnostic
  Liquibase is compatible with a variety of databases including MySQL, PostgreSQL, Oracle, SQL Server, and others, making it versatile for different projects.
• Automated Change Management
  The tool automatically manages database changes and applies changesets using a standardized process, reducing manual management and errors.
• Change History Tracking
  Liquibase keeps a detailed history of all applied changes, allowing for easy audit and rollbacks when necessary.
• Flexible Configuration
  Liquibase offers multiple ways to define database changes, including XML, YAML, JSON, and SQL, providing flexibility based on developer preferences.
• Community and Support
  Liquibase has a strong community and comprehensive documentation, as well as commercial support options for enterprises.

Possible disadvantages

• Learning Curve
  For newcomers, there can be a significant learning curve to fully understand and effectively use Liquibase, especially if they are not familiar with database version control concepts.
• Performance Overhead
  Running Liquibase checks and updates can add performance overhead, especially in large-scale environments with many changesets.
• Complexity in Large Projects
  Managing complex database schemas with many interdependent changes can become complicated and may require meticulous planning and organization.
• Limited GUI Tools
  While Liquibase is powerful, its command-line interface may be less intuitive for some users compared to other tools that offer robust graphical user interfaces.
• Compatibility Issues
  Occasionally, certain database-specific features or custom implementations may not be fully supported by Liquibase, leading to potential compatibility issues.
• Commercial Licensing Costs
  While the core version is open-source, enterprises may require commercial licenses for advanced features, which can add to the overall cost.

• User-Friendly Interface
  Plotter offers a clean and intuitive user interface, making it easier for users to focus on writing and plotting without getting lost in complex menus or features.
• Story Planning Tools
  Plotter provides robust story planning features, such as timeline, outlining, and character development tools, which help writers organize and structure their stories effectively.
• Cross-Platform Compatibility
  Plotter is available on multiple platforms such as Windows, macOS, and mobile devices, allowing users to access their projects across different devices with ease.
• Collaboration Features
  The app supports collaborative features, enabling writers to share projects and work together in real-time, which is beneficial for team projects or writing partners.

Possible disadvantages

• Limited Customization Options
  While Plotter offers excellent structure and planning tools, it may lack customization options for users who have specific needs or prefer more flexibility in their workflows.
• Subscription Cost
  Plotter operates on a subscription model, which may be a drawback for some users who prefer a one-time purchase or are looking for free alternatives.
• Learning Curve
  New users might experience a learning curve as they get accustomed to Plotter’s features and functionalities, especially if they are used to more traditional writing tools.
• Offline Availability
  Some users might find the offline capabilities limited, as the app may require internet access for certain features or for syncing across devices.

Version based database migration with Liquibase

More videos

No Plotter videos yet. You could help us improve this page by suggesting one.

• How do you guys go about the persistence layer?

  As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: over 4 years ago

• How do you guys go about the persistence layer? (x-post)

  I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: over 4 years ago

• Where questioning the scale of a company and its clients its seen bad

  Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: over 4 years ago

View more

Tracking Plotter since Mar 2022.