Understand what you’ll do in the tutorial and why layers matter.
main
and deploy it to “staging” so they could test it in a production-like environment. Then, if there are bugs, developers would have to rush and do a lot of rework to fix main
, which would now be broken.
Even if developers can deploy to “staging” before merging code, usually there will be a confusing Slack channel in which everyone fights for a time slot to use “staging”.
Additionally, developers’ machines may not be powerful enough to run minikube, the whole Elastic Stack, and your own services. Consequently, developers will all point to the same “staging”, causing all sorts of weird bugs as their changes will interfere with one another.
Workers, for example, would be a nightmare because developers’ workers would be competing with each other to pick up messages from a queue.
That’s not to mention all the problems related with residual and messy data that will remain in staging
.
Layerform solves all of these problems by allowing each developer to create their own “staging”. In each “staging”, developers would have their own Elastic Stack, and any other services they may need. That way, developers’ changes and tests won’t interfere with one another.