The solution's documentation available over the internet is not straightforward and customer-friendly. The documentation is mostly for the on-prem services, and there's no documentation for the cloud offering, which could be improved. The pricing is not readily explained over the internet, and I had to manually check a lot of forums to get an insight into how we are getting charged. We were on a pro plan, and JFrog could have suggested optimization or plan upgrades based on our utilization. That didn't happen unless we manually looked into it, and now we are considering moving away from this platform. The solution's storage costs are getting too high. Last month, we were charged around two and a half terabytes, which is a lot of data. We are considering moving towards a cost-effective platform.
In my experience, there was a bit of a learning curve at the beginning. It can be somewhat challenging to install and get started. However, once you gain some experience, working with JFrog becomes much easier. Overall, it's manageable for beginners, but there might be a bit of a learning curve. I'd call myself an intermediate user.
One challenge we face is related to performance. Our integration involves GitHab and JFrog Container Registry, with pipelines fetching data from GitHub and JFrog Container Registry for third-party code. However, there are instances where this process can slow down the pipeline.
The Container Registry solutions are designed for managing, storing, and securing container images. These registries serve as pivotal elements in the deployment pipelines of modern software development, especially in environments leveraging microservices architecture and containerization technologies like Docker and Kubernetes.
The solution's documentation available over the internet is not straightforward and customer-friendly. The documentation is mostly for the on-prem services, and there's no documentation for the cloud offering, which could be improved. The pricing is not readily explained over the internet, and I had to manually check a lot of forums to get an insight into how we are getting charged. We were on a pro plan, and JFrog could have suggested optimization or plan upgrades based on our utilization. That didn't happen unless we manually looked into it, and now we are considering moving away from this platform. The solution's storage costs are getting too high. Last month, we were charged around two and a half terabytes, which is a lot of data. We are considering moving towards a cost-effective platform.
In my experience, there was a bit of a learning curve at the beginning. It can be somewhat challenging to install and get started. However, once you gain some experience, working with JFrog becomes much easier. Overall, it's manageable for beginners, but there might be a bit of a learning curve. I'd call myself an intermediate user.
One challenge we face is related to performance. Our integration involves GitHab and JFrog Container Registry, with pipelines fetching data from GitHub and JFrog Container Registry for third-party code. However, there are instances where this process can slow down the pipeline.