AWS Amplify vs GitLab comparison

"One of the things I like best about AWS Amplify is its ease of use and strong integration with other AWS services, which enhances efficiency."

"I didn't host my application but have used their backend as a service. It was a complete package with authentication, AWS AppSync, DynamoDB, and GraphQL. AWS Amplify is great if you don't know backend development and don't want to struggle with other backend services like MongoDB. You don't have to worry about what backend language or database to use. If you're confused, enroll with AWS Amplify. I also recommend Google Firebase for similar purposes."

"The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support."

"The most valuable feature is user management, which includes authentication and authorization."

"Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as needed. They don't necessarily need to involve the cloud team for basic management."

"The most valuable feature of AWS Amplify is authentication."

"The link with Figma is very nice. You can create your design in Figma, and then you can import it into AWS Amplify and use it. You can link it to your data source and data bindings."

"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."

"The stability is good."

"The SaaS setup is impressive, and it has DAST solutioning."

"The initial setup of GitLab is pretty simple, with no complications."

"The most valuable features of GitLab are the review, patch repo, and plans are in YAML."

"The user interface is really good so that helps with huge teams who need to collaborate."

"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."

"GitLab is a solution for source code management, container registry, pipelines, testing, and deployment."

"I like AWS Amplify's documentation. It's comprehensive and includes many examples, so you don't need to ask for help much - you can refer to the docs. It's easy to use. I also appreciate the cost structure. You only pay for what you use. For example, if you use 100 GB, you're charged for that, but if you don't use it, you pay the maintenance cost."

"AWS can implement multiple web applications, and cross-platform applications, like iOS."

"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."

"Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects."

"I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs."

"AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options."

"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."

"It should be used by a larger number of people. They should raise awareness."

"Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms."

"The solution does not have many built-in functions or variables so scripting is required."

"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."

"I'm new to GitLab, so I would appreciate more documentation about the code and commands."

"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."

"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."

"GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users."

"The pricing depends on what your use case is and whether you're an existing AWS customer. It's a pay-as-you-go model, so not expensive."

"When you're just starting, it is free. You have to pay only when you reach a certain amount of usage. I'm still at the early stage. So, I don't have to pay a lot. At the moment, it is not too expensive for me. It is worth the money."

"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."

"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."

"It seems reasonable. Our IT team manages the licenses."

"The solution is based on a subscription model and is reasonably priced."

"I think that we pay approximately $100 USD per month."

"In total, I believe we have more than 300 licenses spread over about 100 users, though I can't comment on the costs involved."

"We are using the open-source version."

"The price is okay."