Which two statements are correct about microservices?

A microservice architecture allows for highly scalable and maintainable application designs, and one of its key benefits is the ability to add new microservices without incurring system downtime. This is made possible because microservices are designed to be independently deployable and extensible components that perform specific functions. When a new microservice is developed, it can typically be deployed alongside existing services without the need to take the entire system offline. This ensures a smoother user experience since new functionalities can be introduced while the system remains operational.

In particular, this approach enables continuous delivery and integration practices, where features can be rolled out incrementally and independently. The added microservice can work in conjunction with others, allowing for greater flexibility and quicker responses to market needs or user requests.

Other options suggest various constraints that are not generally true of microservices. For instance, the assertion about needing system downtime for updates contradicts the whole premise of microservice architecture, which advocates for minimal interruptions during updates and maintenance. While hosting requirements can vary, the idea that a microservice must always reside on a separate server is overly restrictive, as microservices can also be containerized and share resources as needed.