Share your experience using Flockport

I use it to containerize microservices. It's a comprehensive container solution for managing microservices.

It streamlines the operation of our e-commerce systems for major brands, making deployment easy and cost-effective.

It significantly simplifies our deployment and management processes. We've containerized over ten microservices, improving efficiency and deployment speed.

For Kubernetes management, the key thing is managing containers. It reduces errors compared to traditional servers. Since containers are lighter weight, deploying them is faster. Think about it this way - if an image is smaller and lighter, you can install it much quicker. This is especially beneficial when you need to deploy a large number of containers, potentially in just minutes or even seconds.

The multi-cloud support has positively influenced our maintenance and operational efficiency.

More integrations with other platforms would be beneficial.

I have been using it for more than five years. 

It is a stable solution. It is nearly perfect. I would rate the stability a ten out of ten. 

It is a scalable solution. I would rate the scalability a ten out of ten. 

It was extensively used in our company. There were around a thousand end users using it. 

Deployment time varies depending on the cluster configuration. Sometimes, it can take days. It depends on the configuration of the clusters. In some cases, like the configuration assessment can take longer. But that's not because of Docker itself.

It's just because we might not have information about the Docker configuration, for example. Let's say you have a cluster in another Kubernetes environment, and you want to use a port from that other cluster on your current Kubernetes cluster. That can make things more complex.

We used a consultant's help.

I recommend it.

Overall, I would rate the solution a seven out of ten. 

We use Mirantis Container Cloud to package and configure our microservices. Whether it's a simple standalone service or a service with a PostgreSQL or MongoDB connection, we handle it all in a Docker file.

We don't use Mirantis Container Cloud straightforwardly. We use it through GCP and Google's managed Kubernetes environment.

Mirantis Container Cloud operates similarly to how we interact with databases. It provides a comprehensive platform for deploying and managing containerized applications across cloud environments.

The solution makes it easy to reconfigure your microservices. Each microservice has its configuration stored in one file. If you need to scale or perform any other action, you can access these configuration files and scale the specific part of your system. This approach divides the system into manageable pieces while keeping them interconnected. The configurations are centralized, preventing scattered configurations across random places.

The solution's stability could be improved. 

I have been using Mirantis Container Cloud for two years.

Mirantis Container Cloud is designed to facilitate easy setup and reconfiguration of microservices. Each microservice has its configuration stored in a single file. Scaling or adjusting components can be achieved by modifying these Docker files. This approach breaks down the system into manageable pieces while ensuring coherence and centralized configuration management. Overall, it offers stability and ease of management.

I rate the solution’s stability a nine out of ten.

The solution is scalable.

We have a dedicated team that handles all requests. They can contact support for issues like Postgres or anything else. In the past few years, we've encountered some problems with containers around five times, but our team has managed to address them effectively.

The initial setup is straightforward but requires some knowledge and research to be executed properly. Once you understand the process, it becomes simple, involving configuration in one file. It is easy to reconfigure

Google provides us with GKE, a managed global cloud Kubernetes engine. We've deployed our application there. It's familiar territory for us, and scaling up or down is incredibly simple. Our workflow revolves around GitHub actions and a specific set of configurations. 

You have support for multiple configurations. Let's say you need a service that uses a SQL database; perhaps you require another well-known SQL database. With Mirantis Container Cloud, you can configure all these in one place. Additionally, these services can connect seamlessly. You can specify the ports on which they connect in a single configuration file, consolidating all settings in one central location.

All these cloud platforms—Google, Amazon, Microsoft Azure, and others—offer a managed Docker environment.

We are also using Mirantis Container Cloud for development. It simplifies the setup needed for your project. Instead of installing various components individually on your Windows or IOS, such as a SQL database, a NoSQL database, DocIQ, with Docker, you can install everything within Docker containers. This keeps your project setup separate from your computer's environment. It's really convenient, if you need to transition to a different project with different requirements. You can simply discard the Docker images associated with the previous project and install the new ones for the new project. This process doesn't affect your computer, whether it's running Windows, Mac, Linux, or any other operating system.

It's a great solution. It's designed to handle complex, demanding, and scalable applications. Occasionally, these issues can be challenging to investigate, necessitating support intervention. I recommend this solution.

If you would like to scale your application to get millions of end users. It offers the biggest scalability.

Mirantis is simplifying their setup, stability and the easy use of configuration.

Overall, I rate the solution a nine out of ten.