Liquibase VS Codekeeper

• 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.

• Cloud-based Access
  Codekeeper is a cloud-based service, making it accessible from anywhere, which is convenient for remote teams and developers working across different locations.
• High Security
  Offers secure version control with robust security features, ensuring that the source code is protected from unauthorized access.
• Automated Backups
  Provides automated backup solutions, allowing users to easily schedule backups and ensure data integrity.
• Integration Capabilities
  Can be integrated with various other tools and services, enhancing its utility and allowing teams to streamline their workflows.
• User-friendly Interface
  Comes with an easy-to-use interface that helps users quickly navigate and manage their code repositories.

Possible disadvantages

• Cost
  The service might be costly for smaller teams or individual developers, especially when compared to free alternatives.
• Limited Offline Functionality
  Being cloud-based means there may be limited capability for offline access, which could be a drawback in environments with unreliable internet connections.
• Learning Curve
  New users may experience a learning curve associated with understanding and fully utilizing all of Codekeeper's features.
• Dependence on Internet
  Access and functionality are heavily dependent on a stable internet connection, which might hinder use during outages.
• Customization Limitations
  There may be limited scope for customization according to specific needs, as compared to some more flexible self-hosted solutions.

No analysis of Codekeeper yet.

Version based database migration with Liquibase

More videos

Codekeeper - Source Code Escrow Platform Demo

• 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

• Ask HN: What code escrow companies do you recommend?

  I had a similar requirement recently and ended up going with CodeKeeper (https://codekeeper.co/), mainly because they had a portal that seemed mostly self-serve. Because they are based in The Hague, and because my client had domestic... - Source: Hacker News / 10 months ago