Skip to content

Latest commit

 

History

History
303 lines (293 loc) · 19 KB

readme.md

File metadata and controls

303 lines (293 loc) · 19 KB

🎓 MJC school : EPAM Systems
Minsk, Belarus (Минск, Беларусь)
module #2. REST API Basics

♟ Business requirements

  1. Develop web service for Gift Certificates system with the following entities (many-to-many):
  2. The system should expose REST APIs to perform the following operations:
    • CRUD operations for GiftCertificate. If new tags are passed during creation/modification – they should be created in the DB. For update operation - update only fields, that pass in request, others should not be updated. Batch insert is out of scope.
    • CRD operations for Tag.
    • Get certificates with tags (all params are optional and can be used in conjunction):
      • by tag name (ONE tag)
      • search by part of name/description (can be implemented, using DB function call)
      • sort by date or by name ASC/DESC (extra task: implement ability to apply both sort type at the same time).

📺 Application requirements

  1. JDK version: 8 – use Streams, java.time.*, etc. where it is possible. (the JDK version can be increased in agreement with the mentor/group coordinator/run coordinator
  2. Application packages root: com.epam.esm
  3. Any widely-used connection pool could be used.
  4. JDBC / Spring JDBC Template should be used for data access.
  5. Use transactions where it’s necessary.
  6. Java Code Convention is mandatory (exception: margin size – 120 chars).
  7. Build tool: Maven/Gradle, latest version. Multi-module project.
  8. Web server: Apache Tomcat/Jetty.
  9. Application container: Spring IoC. Spring Framework, the latest version.
  10. Database: PostgreSQL/MySQL, latest version.
  11. Testing: JUnit 5.+, Mockito.
  12. Service layer should be covered with unit tests not less than 80%.
  13. Repository layer should be tested using integration tests with an in-memory embedded database (all operations with certificates).

🗿 General requirements

  1. Code should be clean and should not contain any “developer-purpose” constructions.
  2. App should be designed and written with respect to OOD and SOLID principles.
  3. Code should contain valuable comments where appropriate.
  4. Public APIs should be documented (Javadoc).
  5. Clear layered structure should be used with responsibilities of each application layer defined.
  6. JSON should be used as a format of client-server communication messages.
  7. Convenient error/exception handling mechanism should be implemented: all errors should be meaningful and localized on backend side. Example: handle 404 error: 
     • HTTP Status: 404
 • response body    
 • {
 • “errorMessage”: “Requested resource not found (id = 55)”,
 • “errorCode”: 40401
 • }
    where *errorCode” is your custom code (it can be based on http status and requested resource - certificate or tag)
  8. Abstraction should be used everywhere to avoid code duplication.
  9. Several configurations should be implemented (at least two - dev and prod).

⚠ Application restrictions

  1. Spring Boot.
  2. Spring Data Repositories.
  3. JPA.
  4. Powermock (your application should be testable).

📚 Extra Materials

  1. Java 8
  2. Coding best practices
  3. Exception handling
  4. Layered Architecture
  5. Spring Framework
  6. REST API Fundamentals
  7. Connection Pool
  8. Maven
  9. Testing
  10. Postman