Continuous Delivery

By the end of Scene 4, you were able to deliver on a vision and release an application to users.

The real challenge begins upon release. After a successful release many different issues may arise in the application, like aspects of the application that you want to improve or the addition of new features and functionalities.

With the skills to be learned in this scene, gain the ability to quickly find problems, make improvements smoothly, and continue to deliver your application to users.

  1. Continuously Improve the Application and Deliver Quickly to Users


    While issues can come up when developers want to add features or improve a functionality, as long as they are able to get a hold on the problem and deal with development quickly, it's possible to deliver the newest version of the application to users in a stable state. Implementing CI/CD automates processes that would otherwise be conducted separately: testing, building, deploying, and so on. Conduct these processes continuously to improve the speed and quality of development.

  2. Improve the Application By Understanding the Usage

    Data Analytics Fundamentals

    Getting a feel for the state of an application; the behavioral tendencies attributed to each type of user, frequently used content, etc., can be gotten through the collection and analyzing various data taken from the system. Understanding the state of an application brings forward problems that may exist in a product and helps lend itself to the implementation of processes for improvement. This all leads to delivering an even better user experience. Take the steps to make the application better through learning about how data collection and analysis works.

  3. Improve the User Experience


    Areas of improvement in a product aren't just getting rid of errors or fixing bugs. When there are problems with performance it can deteriorate the user experience with irritators like web pages taking a long time to load and clicks having trouble registering. Improve the application and help make the experience pleasant for the users.

  4. Create a Structure That Continues to Work Even with a Rise in Users


    A sharp rise in users or server failures causes the workload of a system to increase. As a result, problems such as drops in performance or pauses in services will occur. In order to be capable of delivering a stable service to users make sure that hardwares, databases, and applications have the ability for expansion.

  5. Become Able to Deal with Service Issues

    Fault Tolerance

    System failures. Every once in a while a failure in a system can negatively affect the service, keep developers in a day to day fear of them happening, and stress out users who can't use a service because of them. Become a developer who can create a product that can avoid the stoppage of service even if a failure occurs.