I recommend the product for end-to-end development for highly scalable, distributed, and microservices, where there are more than 100-200 services integrating together to build a platform.

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

I rate CircleCI an eight out of ten.

I rate the product as a nine out of 10 because it is intuitive, easy to configure using the Circle.yml file, and supports container-based builds. I’m taking off one point out of 10 only because, at the time of using this product, it doesn’t have deep Microsoft Azure integration.

One piece of advice would be to consider which cloud you are going to be building on, and see if CircleCI integrates well with it. Secondly, I would advise you to try out the free version before implementing because sometimes, if the project is simple enough and if it doesn’t have a whole lot of developers (such as in startup environments) there’s no need to get more containers building in parallel.

AWS provides more options with Jenkins. Jenkins has plugins to work with AWS. And they are able to achieve more complicated tasks. Such as triggers.