Kubernetes vs. Liquibase

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

Store versions of DB's and Schemas this is useful for every software developer company that works with Databases. Now days al the software use a DB and control those changes are a must. have the power to rollback safe has change the way that we work. This increase speed in development while increase the business confidence.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• It's a useful tool for managing database versions and aiding in the development of database CI/CD pipelines.
• The deployment and management of database updates are simple.
• It provides quality checks to spot problems in DB scripts and DB pipeline views to track changes made to DB.

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
• We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
• Liquibase should rollback the if any one of the changes fails.

Incentivized

We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.

Incentivized

Build process is too time consuming and getting extra DB instance takes a toll

Incentivized

Liquibase's customer support is at the top of my list of all vendors I've ever worked with over my 12 years of experience. They work directly with you to be successful, and response time is second to none. Liquibase is committed to getting customers up and running and - more importantly - successful in their organization and becoming champions of the product.

Incentivized

the database deployments helped us with increased productivity,
faster delivery and low risk.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

To be honest, the option of having a free community plan to start testing in a test environment, followed by taking it in production a few months is a great way to evaluate wether or not to do the subscription based plan.

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• We need to re-educate developers to use Liquibase.
• In some cases, it is hard to align when several teams work on the same DB.
• On the other hand, Liquibase provides order and consistency in managing DB changes.
• Evidence and traceability are a plus.

Incentivized