With the sheer amount of software being created today, software development techniques are rapidly and continuously evolving. Even industries that previously had a very fixed cycle, such as car manufacturers, are moving towards continuous delivery. As more companies adopt an Agile development process to support continuous delivery, testing (or quality assurance) and delivery need to keep pace. Hence, the rise of DevOps, which manages the entire product lifecycle. But, there are varying levels of DevOps. In this post, we define those levels and share with you our approach. How does your enterprise measure up?
An often overshadowed aspect of building great products is ensuring these products are reliable and perform as expected. Similar to physical products, the quality of a digital product has a large impact on the customer/user experience. Typically, a quality assurance (QA) or testing team leads this effort. But, what is the difference between QA and testing, and does it matter? We believe so, and so should you.
As mentioned in my previous post, A path to microservices, adopting a microservices architecture is not simple. It requires many prerequisites to be managed successfully. With multiple services you quickly realize how many resources they use. Even the smallest service has a run-time footprint and consumes CPU cycles, even when sitting idle. Multiply this by number of services and you quickly get the picture. This post explores how this can be improved, and if it is possible to go beyond microservices to a serverless architecture.
Developers today most likely can’t imagine not having source control and continuous integration systems. However, one area enterprises may still be struggling with is how to integrate an automated test solution for native mobile applications into a continuous integration workflow. This article provides suggestions on how to do so along with an example of how we did it at Devbridge Group.