Skip to main content

Final Thoughts

If you have gotten to this section, congratulations. We have basically architected a software development cycle and be able to get applications ran on kubernetes. All future applications use everything we have built so far to deploy new applications.

As a review, we have done the following:

  1. Configured on site hardware to run kubernetes.
  2. Configured online services to host code, create containers, and aggregate logs.
  3. Configured services to recieve notifications on code changes, pull requests, and kubernetes actions.
  4. Configured argoCD to automate the majority of deployment.

What do we focus on from now? Remember, the idea is to configure once and just focus on the code. We shouldn't be worried about how things get deployed or updated on a daily basis. These things we want to be methodical but have services help us do it for us. As you move forward in your development cycle, you may make changes to things like deployments or expose your microservices with ports. The best thing here is we are able to develop with minimal impact on your bank account. If you want to do all of this on platforms like Azure or AWS, it's basically the same but the difference being it's all in the cloud. I would caution doing this as with FinTech, the amount of data you push may cause you to have a very large usage bill very quickly.