https://github.com/sugrado/telco-crm-microservices
Telko CRM project using Java and Microservices.
https://github.com/sugrado/telco-crm-microservices
crm eureka hibernate-jpa java java17 jwt kafka lombok mapstruct microservice microservices postgresql spring-boot spring-cloud spring-data-jpa spring-security springframework
Last synced: 3 months ago
JSON representation
Telko CRM project using Java and Microservices.
- Host: GitHub
- URL: https://github.com/sugrado/telco-crm-microservices
- Owner: sugrado
- Created: 2024-04-15T18:01:11.000Z (about 2 years ago)
- Default Branch: master
- Last Pushed: 2024-06-10T16:43:09.000Z (about 2 years ago)
- Last Synced: 2025-10-29T22:35:24.324Z (8 months ago)
- Topics: crm, eureka, hibernate-jpa, java, java17, jwt, kafka, lombok, mapstruct, microservice, microservices, postgresql, spring-boot, spring-cloud, spring-data-jpa, spring-security, springframework
- Language: Java
- Homepage:
- Size: 3.07 MB
- Stars: 0
- Watchers: 1
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.en-US.md
Awesome Lists containing this project
README
# Telko CRM Project with Microservices
This repo includes the **Telko CRM** project developed by the **Pair 2** group within the scope of the **Turkcell GYGY
3.0**
Program. **Microservice** architecture was implemented using the **Java** programming language.
## Development
- [Conventional Commits](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716)
- Use `@Getter`, `@Setter`, ... instead of `@Data` annotation in classes. It provides more modularity and flexibility.
- Package names should be in lower snake case. For example **com.turkcell.crm.customer_service.data_access**
- Database table names should be in lower snake case. For example **crm_customers**
- Use type names instead of the `var` keyword. For example **List customers** instead of **var customers**
- Use record types instead of classes for immutable data. For example request and response objects.
- Rest api standards in the relevant link must be
followed. [REST API URI Naming Conventions and Best Practices](https://restfulapi.net/resource-naming/), [Best practices for REST API design](https://stackoverflow.blog/2020/03/02/best-practices-for-rest-api-design/)
- Finally, review your codes periodically.
## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b /`
3. Commit your changes: `git add . && git commit -m '(): '`
4. Push to the branch: `git push origin /`
5. Submit a pull request.