List the non-functional requirements you know, and tell how they are handled in a microservices architecture.

Non-functional requirements (NFRs) are system characteristics not directly related to business logic but critical for quality and operation. The main ones are:

• Performance (response speed, throughput)
• Reliability (fault tolerance, recovery)
• Scalability (ability to grow with load)
• Security (authorization, authentication, data protection)
• Maintainability (ease of making changes)
• Availability (uptime)
• Operational convenience (monitoring, logging)

In microservice architecture, NFRs are handled as follows:

• Performance is achieved through load distribution among services and the ability to scale each component separately.
• Reliability is increased due to service isolation: failure of one does not lead to system-wide failure.
• Scalability is implemented through horizontal scaling of microservices.
• Security becomes more complex due to multiple interaction points, so centralized authentication systems and channel encryption are used.
• Maintainability improves thanks to clear modularity but requires good documentation and standardization.
• Availability is ensured through replication and load balancing.
• Operational convenience requires advanced monitoring and logging systems, as debugging distributed systems is more complex.

Thus, microservices offer flexibility and scalability but require a thoughtful approach to implementing non-functional requirements.