In this chapter, we learned about different Solidity design patterns that can be used while developing contracts. The design patterns should be used according to your contract's architecture needs. We learned about security, creational, behavioral, economic, and life cycle patterns. Under each category of patterns, we discussed different patterns. We looked at the access restriction, state machine, subscription, tight variable packing, and auto deprecate pattern.
Solidity is a contract-oriented language, hence there are some different kinds of design patterns applied and used. The blockchain ecosystem is relatively new and more such design patterns could evolve over time. It is also possible that the Solidity language itself natively evolves and supports some of the design patterns.
When developing a contract code, it is better to use these design patterns...