Microservice Design And Architecture » Week 1 » Reliable Google Cloud Infrastructure: Design And Process

Q: You’re building a RESTful microservice. Which would be a valid data format for returning data to the client?

Correct. They have a standard Content-Type that can be set on the response header and are text-based. It is usual to use JSON, but both XML and JSON are valid.

Q: You’re writing a service, and you need to handle a client sending you invalid data in the request. What should you return from the service?

Correct. 400 is a HTTP status code indicating that a request could not be processed due to an apparent client error.

Q: Which below would violate 12-factor app best practices?

Correct. Code and config should be separated, because config varies across deployments but code does not. The true test is whether the repository could be open-sourced without compromising any credentials.

Q: You’ve re-architected a monolithic web application so state is not stored in memory on the web servers, but in a database instead. This has caused slow performance when retrieving user sessions though. What might be the best way to fix this?

Correct. Services should be stateless,and a service like Redis or Memorystore provides a fast caching service to store state.They enable services to be stateless and support scale and high availability.