15 Jul Don’t Be An Agile Imitator
An Open Letter By A Monolith
Dear ‘So-Called’ Agile Teams,
I don’t have a dog in this fight. My race is being killed as architectures are modernized to micro-services structures every day. As my owners have not envisioned the problems I will cause them in the future, I have survived so far.
I will have to admit, micro-service & micro-front end methods are much better than my generation. For organizations aspiring to build faster, easier and manageable large, enterprise-grade apps, this is the future. The independence and functionality micro-services offer through decoupling components from each other drives the flexibility needed as customer experience expectations keep redefining themselves.
But some of you are just imitating to be agile! Such a waste, as you have so much to offer to the future of technology. Many of you are using micro-services in the back-end and running them on top of monolith front-end structures. What a pity. The micro-services ideology is not only for your back end, but needs to be inculcated in the entire solution. Please don’t claim to be flexible, lean, and fast without embracing micro-front-ends along with your back-end architecture.
Micro-front ends enables teams to break the front end into independently, deploy-able, micro front-end applications. While micro-services focus on decoupling the back-end services in an application, you guys need to enable your micro-front ends to effectively and efficiently aggregate front-end micro applications. Moreover, they are reusable assets that can be curated as pre-tested front-end assets for the future. More and more new age organizations across industries are already actively using these to enhance their user experience and speed of future feature releases, including IKEA, Fiverr, Starbucks, Spotify, Open Table among-st others as well as future-ready, automated delivery platforms such as #NewAgeDELIVERY looking to help teams to transform applications into truly new age, modernized solutions.
You came and gave back-ends a transformation, effectively taking out people like me, but was your goal only to eradicate me or build strong, resilient, agile systems? Follow through with your vision into the front end as well!
This will allow front ends to be easily scalable, deployed in chunks, enable making UX changes in an agile incremental (learned this work from you, only) fashion, and ensure you develop & deploy with greater accuracy. As solutions reach a large size, decoupling your front end will make more sense to you, and will also allow you to use smaller groups of full stack commando’s to deliver as multiple teams can contribute to micro-front end structures. Further, micro-front ends allow you to turn on & off specific parts to specific users making the user journey more personalized and secure.
In my defense, this transformation to micro-front ends will add to your operational complexity, change your testing patterns, and as multiple teams work and contribute at the same time, challenge accessibility and optimization. Further with each team being independent having unique frameworks and code bases, it can lead to browser ambiguity due to the absence of set standards. But even with this, you are still better suited for the new world, as these issues can be overcome.
Please make the most of who you are, and ensure you are using micro-front ends along with lightweight micro-services architectures. Take it from me: If you only imitate being agile by showing your flexible back-end with a large monolith front end, someone else will come in and eradicate you as well.
I am on my last days, and I have given a lot to the technology evolution we have seen. Now, it is your turn. Call out your imitators, and ensure they are using the right back end & front-end structures in their solution. Please take the baton and guide technology to the next frontier. Unfortunately, I may not be here to see it, but all the very best.
Coupled Together, Always (Unfortunately),
An Old Monolith