Pawan is working as Sr Web developer at JCP, loves to make impact to the customers or masses, comfortable throughout the stack, but presently making difference at front end and devtools.
Yes, it does matter. Remember serverless? Tell me that is not a confusing name.
Anyway, "microfrontends" doesn't say anything useful about the problem they are trying to solve. How micro is "micro". And "frontend"? isn't that the whole user interface how can it be micro? The confusion only increases when someone mentions that it can involve multiple frameworks (how can that still be micro?). If we are talking about independent UI pieces, we already have "components" how is this any diferent?
If you hear "composable apps" things change. "App" means that this thing is independent (maybe a whole team build it), "composable" maybe means that is meant to work along side another app or inside of it.
Replace microfrontend with microservice, and your concern is still valid. Naming is hard:
Anyway, "microservice" doesn't say anything useful about the problem they are trying to solve. How micro is "micro". And "service"? isn't that the whole user system how can it be micro? The confusion only increases when someone mentions that it can involve multiple frameworks (how can that still be micro?). If we are talking about independent api pieces, we already have "request handlers" how is this any diferent?
I really do wish they had a better name for this pattern. Maybe "Composable apps"? can we make that happen?
The way i see it is like Django apps but for client-side javascript.
Does really name matter ?
It's pattern to solve specific problem
Yes, it does matter. Remember
serverless? Tell me that is not a confusing name.Anyway, "microfrontends" doesn't say anything useful about the problem they are trying to solve. How micro is "micro". And "frontend"? isn't that the whole user interface how can it be micro? The confusion only increases when someone mentions that it can involve multiple frameworks (how can that still be micro?). If we are talking about independent UI pieces, we already have "components" how is this any diferent?
If you hear "composable apps" things change. "App" means that this thing is independent (maybe a whole team build it), "composable" maybe means that is meant to work along side another app or inside of it.
Would thinking about it in conjunction with "microservices" and the problems they solve help?
It does help. It would turn it into a dangerous game, we can't just put "micro" in front of everything and hope people understand.
Replace microfrontend with microservice, and your concern is still valid. Naming is hard:
Anyway, "microservice" doesn't say anything useful about the problem they are trying to solve. How micro is "micro". And "service"? isn't that the whole user system how can it be micro? The confusion only increases when someone mentions that it can involve multiple frameworks (how can that still be micro?). If we are talking about independent api pieces, we already have "request handlers" how is this any diferent?
As someone who's half in Django code and half in front-end code, this is the description I never knew I needed. This really makes sense to me.