On all Greenfield projects, the platform building will get stuck and blocked by the application development, and the opposite is also true. We at Boldlink understand that this pace difference should not be a challenge for our customers.
When building an end to end platform across different environments, we are breaking the regular MVP/Greenfield cycle order and most often than not, the platform must be ready before the API Application or Service is.
We have quite a few “pieces” to put together before the applications are deployed, and if you get the wrong order, you will be blocked.
For example, you can’t start using SSL/TLS on your AWS Load Balancer without implementing DNS and Setting up your domain or the proper VPC configuration.
The solution we have built is a small RestAPI we use to simulate a real API and continue with the environment setup steps to a point when a final service or API is ready, and we have a little configuration to change.
This way, independently of the development progress or maturity of the Development Cycle DevOps and Platform teams can:
This application is developed on Python 3. x, we will add additional languages soon and continuously improve it. Check this repo on https://github.com/boldlink/pyhellow
At this phase, the deployment guide is very much coded for Kubernetes. It is in our "TODO list" to add additional Deployments with instructions.