Likelihood to Recommend
Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a
based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.
Read full review
We started to use GitLab for hosting git source code repositories of our projects only but slowly we started to use it to store container images, packages, dependency proxy as well infrastucture registry and it is now well suited for Continuous Integration in our projects, It wasn't that good in Continuous Deployment before 12.0 version but after 12.0 it is amazingly good for Continuous Deployment as well since it keeps deployment information in a well organized manner which can be configure in ci yaml configuration.
Read full review Pros One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues. Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame. Read full review GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions. It helps maintain code stability and reliability, saving time and effort in the development or research workflow. Powerful code review features, enabling collaboration and feedback among team members. Robust project management features, including issue tracking, kanban boards, and milestones. Read full review Cons A cleaner container service road map It would be. nice to have more AI recommended cluster reductions The UX could use some simplification Read full review CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess. Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created. Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy. Read full review Likelihood to Renew
Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.
Read full review Usability
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
Read full review Support Rating
Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.
Read full review
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when
was acquired by Microsoft
Read full review Alternatives Considered
If you are using AWS, you will be using Amazon ECS. I have also used Azure Container Instances and it works just as well in Azure as ECS does in AWS. It's really all a matter of what cloud provider you are utilizing. Because of the "Cloud Wars," it's difficult to measure cross-cloud connectivity, but I have had better luck remaining cloud agnostic in other cloud providers than AWS (Azure, GCP). Because of the sheer volume of tooling in AWS and inter-connectivity between them, it's almost easier to be fully AWS if you are using it in any kind of capacity.
Read full review
GitLab is easily the preferred tool when it comes to versioning and source control. With other tools the UI often feels outdated and clunky leading to inefficiency and confusion. With some of the sleeker tools such as
, while the aesthetic is pleasing, the experience is plagued by a lack of support, lack of optional plugins, and a plethora of bugs that cause unnecessary legwork to resolve. GitLab is the best of both aesthetic and functionality
Read full review Return on Investment We achieved minimum downtime. The autoscaling kept the performance of the services great. We saved money by running the workloads on AWS ECS in Fargate mode by having different settings for different services to save on the hardware configuration side as well as having scheduled tasks. Read full review GitLab issue management has made release smoother, with about a factor 2 less time used by the relevant person The outward facing issue desk now has several hundred public issues answered, and thus alleviates the team, as users can refer to older questions Use of CI has made commitment of faulty code drop drastically Read full review ScreenShots