E-Book, Englisch, 230 Seiten
Alickovic React Application Architecture for Production
1. Auflage 2024
ISBN: 978-1-80107-740-8
Verlag: De Gruyter
Format: EPUB
Kopierschutz: 0 - No protection
Learn best practices and expert tips to deliver enterprise-ready React web apps
E-Book, Englisch, 230 Seiten
ISBN: 978-1-80107-740-8
Verlag: De Gruyter
Format: EPUB
Kopierschutz: 0 - No protection
Building large-scale applications in production can be overwhelming with the amount of tooling choices and lack of cohesive resources. To address these challenges, this hands-on guide covers best practices and web application development examples to help you build enterprise-ready applications with React in no time.
Throughout the book, you'll work through a real-life practical example that demonstrates all the concepts covered. You'll learn to build modern frontend applications-built from scratch and ready for production. Starting with an overview of the React ecosystem, the book will guide you in identifying the tools available to solve complex development challenges. You'll then advance to building APIs, components, and pages to form a complete frontend app. The book will also share best practices for testing, securing, and packaging your app in a structured way before finally deploying your app with scalability in mind.
By the end of the book, you'll be able to efficiently build production-ready applications by following industry practices and expert tips.
Autoren/Hrsg.
Fachgebiete
Weitere Infos & Material
Table of Contents - Understanding the Architecture of React Applications
- Setup and Project Structure Overview
- Building and Documenting Components
- Building and Configuring Pages
- Mocking the API
- Integrating the API into the Application
- Implementing User Authentication and Global Notifications
- Testing
- Configuring CI/CD for Testing and Deployment
- Going Beyond
1
Understanding the Architecture of React Applications
React is an open source JavaScript library for building user interfaces created and maintained by Meta (Facebook).
It is probably the most popular library for building user interfaces nowadays. The reason for its popularity is that it is quite performant and has a small API, which makes it a simple yet very powerful tool for creating user interfaces.
It is component-based, which allows us to split large applications into smaller parts and work on them in isolation.
React is also great because its core API is decoupled from the platform, allowing projects such as React Native to exist outside the web platform.
One of React’s biggest strengths but also weaknesses is that it is very flexible. This has allowed its community to build great solutions. However, defining a good application architecture out of the box can be challenging.
Making the right architectural decisions is crucial for any application to succeed, especially once it needs changes or it grows in terms of size, the number of users, and the number of people working on it.
In this chapter, we will cover the following topics:
- Benefits of having a good application architecture
- Exploring the architectural challenges of React applications
- Understanding architectural decisions when building React applications
- Planning our application
By the end of this chapter, we will learn to think a bit more from the architectural point of view when starting React application development.
Benefits of having a good application architecture
Every application uses some architecture, even without thinking about it. It might have been chosen randomly and might not be the right one for its needs and requirements, but still, every application does have an architecture.
That’s why being mindful of the proper architecture at the beginning is essential for every project. Let’s define a couple of reasons why:
- A good foundation for the project
- Easier project management
- Increased development speed and productivity
- Cost-effectiveness
- Better product quality
It is worth noting that all applications are prone to requirement changes, so it is not always possible to predict everything upfront. However, we should be mindful of the architecture from the start. We will discuss these reasons in detail in the following sections.
A good foundation for the project
Every building should be built on solid foundations to remain resilient to different conditions such as age, weather conditions, earthquakes, and other causes.
The same thing can apply to applications. Multiple factors cause various changes during a project’s lifetime, such as changes in requirements, organization, technologies, market, finance, and more. Being built on solid foundations will make it resilient to all those changes.
Easier project management
Having different components organized properly will make organizing and delegating tasks much easier, especially if a larger team is involved.
Good component decoupling will allow better splitting of work between teams and team members and faster iterations without team members being blocked by each other.
It also allows better estimates to be made regarding how much time is required for a feature to be completed.
Increased development speed and productivity
Having a good architecture defined allows developers to focus on the product they are building without overthinking the technical implementations since most of the technical decisions should have already been made.
Besides that, it will provide a smoother onboarding process for new developers, who can be productive quickly after familiarizing themselves with the overall architecture.
Cost-effectiveness
All the reasons mentioned in the previous sections indicate that the improvements a good architecture brings will reduce costs.
In most cases, the most expensive cost of every project is people and their work and time. Therefore, by allowing them to be more efficient, we can reduce some redundant costs a bad architecture could bring.
It will also allow better financial analysis and planning of pricing models for software products. It will make it easier to predict all the costs the platform requires to be functional.
Better product quality
Making all team members productive gives them time to focus and spend more time on important things, such as the business requirements and the needs of users, rather than spending most of the time fixing bugs and reducing technical debt.
Better product quality will also make our users more satisfied, which should be the end goal.
To exist, every piece of software needs to meet its requirements. We’ll see what these software requirements are in the following section.
Exploring the architectural challenges of React applications
In this section, we will focus on React and see what things are necessary to consider when building React applications and the main challenges most React developers face when building their applications.
What are the challenges when building a React application?
React is a great tool for building user interfaces. However, there are some challenging things we should think about when building an application. It is very flexible, which is both a good and a bad thing. It is good in the sense that we can define the architecture of different parts of the application without the library getting in our way.
By being so flexible, React has gathered a large community of developers worldwide, building different open-source solutions. There is a complete solution for literally any problem we might encounter during development. This makes the React ecosystem very rich.
However, that flexibility and ecosystem richness come with a cost.
Let’s take a look at the following React ecosystem overview diagram made by roadmap.sh:
Figure 1.1 – React developer roadmap by roadmap.sh
As shown in , there is a lot to consider when building an application with React. Let’s also keep in mind that this diagram might show just the tip of the iceberg. Many different packages and solutions could be used to build the same application.
Some of the most frequent questions when starting with a new React application are as follows:
- What project structure are we using?
- What rendering strategy are we using?
- What state management solution are we using?
- What styling solution are we using?
- What data fetching approach are we using?
- How are we going to handle user authentication?
- What testing strategies are we going to use?
These challenges are not limited to React – they are relevant to building frontend applications in general, regardless of which tools are being used. But since this book focuses on React, we will be approaching them from that perspective.
What project structure are we using?
Because React is very flexible and has a very small API, it is unopinionated about how we should structure our projects. Here is what , one of the maintainers of React, says on this:
“”
And that is a very good point. It will mostly depend on the nature of the application. For example, we wouldn’t organize a social network application and a text editor application in the same way because they have different needs and different problems to solve.
What rendering strategy are we using?
It depends on the nature of our application.
If we are building an internal dashboard application, a single-page application is more than enough.
On the other hand, if we build a customer-facing application that should also be public and SEO-friendly, we should think about server-side rendering or static generation, depending on how often the data on the pages are being updated.
What state management solution are we using?
React comes with built-in state management mechanisms with its hooks and Context API, but for more complex applications, we often reach for external solutions such as Redux, MobX, Zustand, Recoil, and others.
Choosing the right state management solution is something that depends a lot on the application’s needs and requirements. We will not reach for the same tools...
