Shulou(Shulou.com)06/03 Report--

The main content of this article is to explain "what are the reasons for considering the use of micro-front-end", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "what are the reasons for thinking about using a micro-front-end?"

1. The application is very small

The first reason is that the application is getting smaller, and you don't have to download a large code base, but just wait 10 minutes to install all the dependencies. Imagine that you joined a company and cloned the repository for the first time, and you had to wait 15 minutes to download the dependency and compile the project. When you look at the source code, thousands of components are written, and you don't even know where to find or make changes, and so on. If your application is small enough, you can browse the application faster and more easily.

two。 Applications are independent

Because all applications are divided and developed separately, they are independent of each other. When you have an overall application, you have too many modules and components that depend on each other, leading to confusion about where to make changes or where to find skins. Imagine a scenario where you have to make some changes in the existing overall application and five different teams are working on it. Sometimes you have to hold a meeting one at a time, and it takes about 2 weeks to find information from all teams. If your application has clearly defined boundaries and allows a dedicated team to focus on it, you can usually save a lot of time.

3. Applications are easier to understand

The application is small and developed by a team, so it is easier to understand. Because these applications have clear boundaries and are developed by a team, they usually follow consistent style guidelines, which makes it easier to understand. For large applications, there are several teams working on it, and they usually do not follow consistent style guidelines. You can even define a good project structure because the number of components or services used for the project is small.

4. Applications are easier to develop and deploy

Because these applications are small in nature and developed by a team, they are very easy to develop and deploy. We can even deploy independently. When you have a build pipeline for large applications on Jenkins, with thousands of components, you need to wait 20 to 40 minutes to download and compile the project. When you define separate pipes for each micro-application, using a micro-front end can greatly reduce these build times.

5. Applications are easier to test

We have to write thousands of unit tests for large applications, and it takes a lot of time to run. This will slow down our deployment process. When it comes to a micro-front end, each application has very few unit tests, performs its own unit tests, and can run independently.

6. Application development becomes faster

With independent teams, the whole development becomes faster and easier.

7. CI / CD becomes easier

Each application can be integrated and deployed separately, which makes the CI / CD process easier. When we fix the application or introduce new features, we don't have to worry about the entire application because all the features are independent.

8. Separate stacks and versions

We can choose our own stack for each application, but this rarely happens, but we can use different versions in the same stack. For example, some teams have the flexibility and time to introduce and test newer versions of the same stack. For example, React is good and flexible to accomplish tasks, while Angular meets other requirements well, and you can choose the framework according to your own needs without having to rely on previous developers or previous teams to start using it. The same applies to different versions of the same framework.

9. No shared code

In large applications, we tend to share code across functions, but this scalability is not good, and as the application grows, it introduces many errors and interdependencies. This doesn't apply to micro-front ends, because we don't share code unless it's a stupid component. We may share information.

10. You can easily change the schema without touching the old schema

Sometimes we have to extend the old architecture, but we may not have developers to implement or extend it. With the help of the micro-front-end approach, we can develop new features with the latest stack and deliver them independently. If you want to extend an existing application that has been around for 20 years, it is difficult to find developers because you must use new technologies to implement the entire application, or you can extend it with the help of a micro-front-end approach.

At this point, I believe you have a deeper understanding of "what are the reasons for considering the use of micro-front-end"? you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.