December 2019 Summaries
2 posts from JFrog
Filter
Month:
Year:
Post Summaries
Back to Blog
Recent developments in the DevOps industry have created uncertainty as major players undergo significant changes, leading to questions about the future of key tools. Docker Enterprise's acquisition by Mirantis, Sonatype's acquisition by a capital firm, and Red Hat's open-sourcing of Quay have left users seeking reliable alternatives amid concerns about the ongoing support and development of these technologies. JFrog positions itself as a stable and trusted alternative, offering solutions like the JFrog Container Registry and Artifactory, along with migration tools and support services to help users transition smoothly from Docker or Nexus. JFrog aims to alleviate concerns by offering to cover remaining contract costs for companies looking to switch, emphasizing its commitment to being a reliable partner in a fluctuating market.
Dec 12, 2019
803 words in the original blog post.
JFrog has expanded its DevOps offerings on the AWS Marketplace by introducing JFrog Container Registry and Cloud Pro X, designed to enhance container management and DevSecOps processes. The JFrog Container Registry, powered by Artifactory, supports Docker, Helm, and Generic repositories, offering a hybrid solution with local, virtual, and remote repositories to facilitate microservices and container adoption across hybrid, cloud, and multi-cloud environments. Available as both an on-premises and SaaS version, it provides flexibility in hosting and infrastructure requirements. Cloud Pro X, integrated with JFrog Xray, offers security vulnerability and license compliance analysis, streamlining DevSecOps with AWS-hosted SaaS to simplify software distribution from code to production. This integration allows users to leverage AWS services like EC2, ECS, and EKS, while benefiting from reduced operational costs, unified billing, and enhanced security management, making it particularly advantageous for those already utilizing AWS as part of their cloud strategy.
Dec 02, 2019
574 words in the original blog post.