# Mission

# Mission Statement

To build and design enterprise APIs with an emphasis on durability, efficiency, maintainability and re-usability.

# Rules to live (code) by

Review Guiding Principles

# Endpoint Naming Patterns

Our path naming pattern is based on starting with the controller (basically the type of data you are after in singular form, and after our standard api/version/ segments), followed by other path segments that further define the request.

A few GET examples;

api/v1/user/{int} default user lookup (userRef)
api/v1/user/by-employeeId/{employeeId} user lookup by employeeId
api/v1/user/detail/{int} default user detail lookup (userRef)
api/v1/user/active listing of active users
api/v1/user/summary/active listing of active users in summary form (i.e. less data)

# MVC Architecture:

https://midfirst.atlassian.net/wiki/spaces/~63f77aeb4c355259db9dd432/pages/3136684051/MVC+Architecture+by+Jason+Denney

MVC Architecture
MVC Architecture