AWS Amplify vs GitLab comparison

"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."

"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 most valuable feature is user management, which includes authentication and authorization."

"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 of AWS Amplify is authentication."

"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."

"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 have found the most valuable feature is security control. I also like the branching and cloning software."

"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."

"The most valuable features of GitLab are the CI/CD pipeline and code management."

"The code merging capability is something that we use very frequently."

"Their CI/CD engine is very mature. It's very comprehensive and flexible, and compared to other projects, I believe that GitLab is number one right now from that perspective."

"CI/CD is very good. The version control system is also good. These are the two features that we use."

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

"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."

"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."

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

"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."

"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."

"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."

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

"The only thing our company is really waiting on in terms of features is the development of metrics."

"Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes."

"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."

"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 solution should be more cloud-native and have more cloud-native capabilities and features."

"There is room for improvement in GitLab Agents."

"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."

"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."

"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."

"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."

"I'm not aware of the licensing costs because those were covered by the customer."

"GitLab's pricing is good compared to others on the market."

"GitLab is highly priced for smaller teams, but it's okay if considering a user base of thousands."

"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten."

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

"The solution is free."

"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."

"We are currently using the open-source version."