Appsmith vs. Azure Pipelines

It is best suited if you want to build a tool for internal use purpose. It is even better suited if you have your data in Google Sheets. You can build apps with functionlity of CRUD where you can not just view but modify and add new entries so you can make good internal CRM tool or HR tool or anything that you need with the flexibility that Appsmith offers.

Incentivized

With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.

Incentivized

• Connect to external data sources like Google Sheets
• Using JS to manupulate data
• Can use JS almost everywhere within design

Incentivized

• Code Integration/Code Deployment
• Azure Engine Auto Scaling Up with help of Pipeline
• Managing Version Control and deploy in rollback with just one click

Incentivized

• UI could be more responsive. Its bit hassle to create a UI which would fit mobile devices.
• If there are multiple UI blocks it gets cumbersome to adjust their size and appearance as you have to do it one by one.

Incentivized

• Error messaging when team members don't have permissions

Incentivized

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

Incentivized

• Saves tons of money to hire a vendor to build apps or hire a specialist within org to build internal apps

Incentivized

• We don't have to deploy changes manually
• But because of this that we automated some tasks, we need to be still aware of some edge cases we can meet and which can cause a pipelines failures
• We can deploy changes pretty fast

Incentivized