Challenge project, the project here aims to practice some of the activities carried out as a back-end developer. The project is a web platform, where you can register an analyst, edit, list and delete, there are basic procedures such as ID already inserted among other business rules created by me, the idea of this platform is to search the database for analysts inserted in the base and be able to search for talent by area or technology, such as Java, Front, DevOps, Angular, SI... You could implement a messaging service to publish as soon as an analyst from that area and technology was added or deleted, the project itself was built using the following technologies;
Back
- Spring boot
- Database h2
- Lombok
- Swagger-ui
- Postman
Front
- Angular CLI: 14.0.7
- Node: 16.15.0
- Npm 8.5.5
- Bootstrap
- Ngx-Bootstrap
- typescript 4.7.4
- Css
API DOCS - OpenAPI
-
Doc
As my work is back-end, even though I have never used it yet, I will use a basic crud with Angular, just to list the services available via rest services, the documentation for the rest services were created via springdoc-openapi, with it it is possible to create the documentation automatically, accessible via uri, and also when creating service documentation in this way, our project receives interfaces created automatically by our yaml file, so it is possible to use a concrete class that is responsible for implementing this interface, for me that I had only acted in the opposite way, creating the controls and then the documentation was very different, today I prefer to work with this concept that when thinking about less is more, this one serves much better.
Called Services Rest on Postman
- Create
- Create Exception
- Get
- Get Exception
- Update
- Get after Update
- Update Exception
- Delete
- Delete Exception
BFF Front
- Home
- Create
- List
- Update and Delete
Back The back-end was created following the best pratices as clean code, clean architecture. Exist improvements to be made with messages more clean, Exception handlers for manager all exceptions in a single place, more validations as bean validations, security with jwt and security in api docs
