Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deciding on Technologies for Backend #202

Closed
3 tasks done
MericKeskin opened this issue Oct 10, 2023 · 2 comments
Closed
3 tasks done

Deciding on Technologies for Backend #202

MericKeskin opened this issue Oct 10, 2023 · 2 comments
Assignees
@bakikucukcakiroglu @bahadirgezer
Labels
effort: low Work requiring very low effort in: backend Work on the backend part of the project in: wiki Work on the wiki section of the repository priority: low Issue not very urgent, can be done later status: done Work is finished type: discussion Topic that needs to be discussed with the team type: research Work that gathers new information
Milestone
Milestone-1

Comments

@MericKeskin
Copy link
Contributor

MericKeskin commented Oct 10, 2023 •
edited by bahadirgezer
Loading

The technologies that will be used by Backend team will be argued. The outcomes should be inspected by other teams for the coherence.
@MericKeskin MericKeskin added status: to-do Something that someone will need to do priority: high Very urgent issue, needs to be done A.S.A.P. type: research Work that gathers new information in: backend Work on the backend part of the project in: wiki Work on the wiki section of the repository labels Oct 10, 2023
@MericKeskin MericKeskin changed the title Decide on technologies for Backend Deciding on Technologies for Backend Oct 10, 2023
@MericKeskin MericKeskin added type: discussion Topic that needs to be discussed with the team priority: low Issue not very urgent, can be done later effort: low Work requiring very low effort and removed priority: high Very urgent issue, needs to be done A.S.A.P. labels Oct 10, 2023
@bakikucukcakiroglu
Copy link
Contributor

I believe that Java Spring would be the most suitable choice for our backend services. It boasts a large community and offers numerous libraries, making it ideal for the efficient and rapid development of services. Furthermore, the fact that everyone on the backend team is already familiar with this technology is a significant advantage.

In terms of the database, a relational database aligns well with our requirements and is considered a best practice when using Java Spring. Given my prior experience, I would recommend using MySQL.

@bahadirgezer
Copy link
Member

Spring would be a good choice mainly because of our affinity with it. It's a flexible framework with powerful functionality. Also it's quick interoperability with different databases, quick configuration, easy layering, and easy serialization-deserialization configurations.

@bahadirgezer bahadirgezer added status: done Work is finished and removed status: to-do Something that someone will need to do labels Oct 13, 2023
@bakikucukcakiroglu bakikucukcakiroglu added this to the Milestone-1 milestone Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bakikucukcakiroglu bakikucukcakiroglu

@bahadirgezer bahadirgezer

Labels
effort: low Work requiring very low effort in: backend Work on the backend part of the project in: wiki Work on the wiki section of the repository priority: low Issue not very urgent, can be done later status: done Work is finished type: discussion Topic that needs to be discussed with the team type: research Work that gathers new information
Projects
None yet
Milestone
Milestone-1
Development

No branches or pull requests
3 participants
@bakikucukcakiroglu @bahadirgezer @MericKeskin