Are common design patterns applicable for microservice architectures?

As part of my master's thesis, I am currently working on a framework for building microservice-based service systems. Based on my research, I am able to define important design criteria that the system must fulfill. In order to make these design criteria usable in practice, I want to draw on proven design patterns. However, since I have little experience in the topic of design patterns so far, I would like to ask two questions:

1. Are the common design patterns (Creational, Structural, Behavioral) suitable for describing microservice-based applications, since they are already several years old?
2. Can the design patterns be combined with each other?

As a concrete example (see image below): The architecture at hand provides for several independent services, which in turn are built on individual microservices (service n). A client request to one of these services is handled by a central microservice that delegates the request to the appropriate microservice behind this Facade. In addition, each service can access a central DataLake that holds, eg., required master data for service execution. This one falls (according to my current knowledge) under the categorization as a Singleton. Is this design methodologically feasible?