Application Architectures & API Design

What architecture pattern is shown here?

• Microgateways

• Microservices

• Model-View-Controller

• Self-contained systems

A microservice should be

• strongly coupled to other services

• service many different purposes

• autonomous

• hard to scale

A microservice should be...

• serving one purpose

• maintained by multiple teams

• directly access databases of other services

• have low cohesion

Monolithic application architectures make sense to use when...

• you need to ensure strong data consistency.

• you have many different engineering teams.

• you need to prioritize scalability over performance

What is NO benefit of using a microservice system architecture?

• Technology Heterogenity

• Resiliency

• Scalability

• Low latency

What does disposability describe?

• To develop low-effort code that can be discarded if not needed

• The possibility to "throw away" a running application instance

REST is a programming language to code microservices

• True

• False

Which HTTP method should be used to replace an existing resource?

• POST

• UPDATE

• PUT

• PATCH

Why should you version your APIs?

• To not break existing clients with changes that are not backward compatible

• To let everyone know about your new fancy features

What is the name of the industry standard for API specifications?

• Frogger

• OpenAPI

• YAML

• Hapi