Deis Workflow VS Modify

• Container Orchestration
  Deis Workflow simplifies the deployment, management, and scaling of containerized applications by leveraging Kubernetes, providing a robust platform for automating container operations.
• Git-based Deployments
  Developers can deploy applications using git push, which streamlines the development workflow and simplifies the deployment process.
• Modular Architecture
  With its microservices-based architecture, Deis Workflow allows for flexible scaling and easy addition of new features or integration with other services.
• Supports Multiple Languages
  Deis Workflow supports a wide range of programming languages, allowing developers to deploy various types of applications without being limited to a specific technology stack.
• Open Source
  As an open-source project, Deis Workflow allows for community contributions and provides transparency, flexibility, and no licensing fees.

Possible disadvantages

• Complex Setup
  Setting up Deis Workflow requires a solid understanding of Kubernetes and container technologies, which can be challenging for teams not already familiar with these systems.
• Dependent on Kubernetes
  Deis Workflow is tightly integrated with Kubernetes, meaning its functionality and feature set are dependent on the Kubernetes ecosystem's maturity and stability.
• Limited Built-in Monitoring
  Out of the box, Deis Workflow offers minimal monitoring and logging capabilities, necessitating additional integrations or tools for comprehensive monitoring.
• Ecosystem Competition
  There are many other container orchestration platforms available, such as Docker Swarm and OpenShift, which might offer more robust features or easier setup, depending on the organization's needs.
• Maintenance and Updates
  As Deis Workflow is open-source, keeping up with updates and ensuring compatibility with new Kubernetes versions requires ongoing maintenance effort and technical understanding.

• No-code website modifications
  Modify allows users to make changes to their websites without needing to write code, making it accessible for non-developers who want to customize their web presence quickly.
• Easy A/B testing and personalization
  The platform enables users to run A/B tests and personalize website content for different audiences without requiring developer involvement, speeding up optimization efforts.
• Quick deployment
  Changes can be deployed rapidly through Modify's interface, bypassing the traditional development cycle and reducing time-to-market for website updates and experiments.
• Visual editor
  Modify provides a visual editor that lets users point-and-click to make changes on their site, making it intuitive and reducing the learning curve for new users.
• No impact on site codebase
  Since modifications are applied as an overlay rather than directly changing the source code, the original codebase remains clean and unaffected, reducing the risk of breaking existing functionality.

Possible disadvantages

• Limited awareness and community
  Modify is a relatively niche tool with a smaller user base compared to established competitors like Google Optimize or Optimizely, which means fewer community resources, tutorials, and third-party integrations.
• Performance concerns
  Applying modifications via a third-party script layer can introduce additional page load time or cause flickering effects as changes are rendered on top of the original page content.
• Limited customization depth
  While the no-code approach is convenient for simple changes, more complex modifications or deeply integrated features may still require developer intervention, limiting what can be achieved through the platform alone.
• Dependency on third-party service
  Relying on Modify means your website changes are dependent on their service uptime and continuity. If the service goes down or shuts down, applied modifications could be lost.
• Potential SEO implications
  Client-side modifications applied via JavaScript overlays may not be fully recognized by search engine crawlers, which could lead to discrepancies between what users see and what gets indexed.

• Why did the Krustlet project die?

  Https://deis.com the guys behind the krustlet blog redirect to azure kubernets page, so maybe they where bought out, and no community effort remained to continue development... Wild guess. Source: almost 4 years ago

• Eli5 What is Kubernetes, containers, etc.?

  Over at Deis, we’ve been busy building open source tools for Kubernetes. We’re just about to finish up moving our easy-to-use application platform to Kubernetes and couldn’t be happier with the results. In the Kubernetes project we’ve... Source: over 4 years ago

Tracking Modify since Mar 2021.