-
Notifications
You must be signed in to change notification settings - Fork 132
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.
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
Build interfaces around our postgres access #2121
Comments
Which databases other than postgres are we expecting Armada to deal with? |
At the moment our main user will be using Postgres. Generally our goal with this is to allow other relation databases so some that come to mind are MSSQL (Microsoft SQL Server), SQLLite, MySQL and Postgres. I don't think we should directly support these in Armada until there is a request to support them. But what I would like to do is to start changing the code so that we could plug and match other databases. |
I am interested too in this sir |
https://developers.google.com/open-source/gsoc/timeline I suggest getting familiar with our project. I've created some other issues for people to play around with. We are excited to have this much interest but I ask that you don't take this project unless you are officially allowed to do so via GSOC application. |
I would say abstracting as necessary so that SQLite or Postgres can work interchangeably is a good concrete starting point, as we could then use SQLite for running unit tests instead of requiring Postgres. The existing tests with SQLite db provider would provide an indicator of success. |
We're using postgres-specific SQL calls for performance (specifically, the postygres-specific copy wire protocol). |
@severinson what's your suggestion for how to solve the underlying issue (we need PG to run unit tests)? I'm pretty sure you expressed an interest in having them run quickly. :) |
I think there are two benefits -- less external dependency for unit tests and more openness in the system which might aid adoption. As long as we keep the postgresy performance stuff in that provider, I don't think it's counter-productive. |
No, this project is still valid, please proceed!
…On Fri, Feb 24, 2023 at 12:57 PM Maureen Ononiwu ***@***.***> wrote:
Does this mean this is no longer a gsoc project?
—
Reply to this email directly, view it on GitHub
<#2121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEO3Y3W6UW77XUQXF6KIL3WZDZAZANCNFSM6AAAAAAU4DDELQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Is this project valid then can I proceed to learn more about it? |
Is this project going to be a part of LFX summer this year? |
Applications open up on May 10th. |
Hey @kannon92. I want to work on this project under LFX summer mentorship. I am a new contributor to this project. How should I get started? Is there any good-first bug that needs attention, I would be happy to help. |
Hello everyone, I am also interested in this issue and would like to join this as LFX mentorship. Can you help me to get started with this project and issue? |
Yeah sure @i-am-yuvi. what kind of help do you need? The issue at hand is that Armada currently only supports the PostgreSQL database for its operations and users are not able to bring their own SQL databases into the system. This limits the flexibility of Armada as some users may have existing databases that they prefer to use instead of PostgreSQL. In order to solve this issue, Armada needs to build interfaces that allow users to use their own SQL databases. This means creating a common interface that abstracts the underlying database implementation details, allowing Armada to work with multiple database types without needing to know the specifics of each one. For more help I would suggest you join the slack channel |
Hey @satyampsoni. If you are already working into this issue. Will you mind if you could share some resources to get started with this project. |
First of all, I would suggest you understand what is Armada and the problem it is trying to solve, You can read the readme it explains it well and talking about the resources those are mentioned in the readme and I am mentioning some links here too. I am also looking forward to working on it during LFX and am also researching more about it. I'll be sharing the resources in the Slack channel as I progress with the issue, I just came to know about this issue last day. Again pls join the Slack channel people there will definitely help you. |
Thanks for this @satyampsoni, I'll definitely join the slack channel |
Hey, I would love to work on this project. I am familiar with Golang and have a good understanding of MySQL and SQL. I am also highly interested in applying for the LFX mentorship program during the months of June and August. |
I am also interested in this can somebody paste the slack channel link here. |
I am interested in this as I have knowledge of Go and SQL databases. How can I go from here as I would like to join and also apply for the LFX mentorship program |
I think this is the link to our Slack -- https://cloud-native.slack.com/archives/C03T9CBCEMC. If that doesn't work, find #armada channel once signed in. |
Apply for the fellowship here: https://mentorship.lfx.linuxfoundation.org/project/73d90321-62b3-498e-bf37-d899ec99df9e |
/assign |
We should make sure that users could bring their own SQL databases into Armada. Currently we only allow postgres as our db but we should create an interface and potentially allow other databases.
This could help with test improvement as we can add mocks for SQL calls and allow us to run unit tests without an active database.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: