Design patterns for building distributed, resilient, and scalable web applications are well known today. However, setting up a project organization to build them effectively remains a challenge, especially when the team itself is distributed. The "human" factor is a source of problems that are difficult to predict.
What would happen if you could take inspiration from the architecture of your applications to improve the communication of your teams?
Microservices, messages queues, load balancers, caches, sharding, decoupling... These architectural concepts are designed to improve digital exchanges within our apps, and above all to anticipate and manage failures. By modeling the exchanges within your team as software architecture, we will see how these design patterns can also be effective in solving our communication issues, very human this time.
You've probably seen these new smartphones with foldable screens, like the Samsung Galaxy Fold, or with two screens like the Surface Duo. They're already on the market, so it's up to you to update and rethink your web apps for these devices! But how? Where to start? Fortunately, the web is constantly evolving and has already started adapting for these new devices, thanks to new APIs.