-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Adding new service to save orders to database #912
Comments
I like this idea, but I wonder if we can use Postgres here as a shared database that can do both the Feature flag service and this new order persistence service. |
Yes, it should work too :) Ideally, we should have opportunity to deploy various types of DBs (MySQL, PostgreSQL, MongoDB) and enable them in helm chart, so we could give a user (vendor) opportunity to test/showcase particular DB connection. From the service perspective it shouldn't be a problem as we could use env variable to choose DB which is currently used. |
Hello @jpkrohling @austinlparker could you assign this issue to me? |
Hello @puckpuck this is a run down of how I'm going to implement at least for what we want to achieve
Of course we can add options for users to specify other database types to use later on. |
@Kimbohlovette , I don't think we need a new service for this. The Also please call the database service |
@Kimbohlovette and @puckpuck I think we need to discuss further this before starting implementing. AFAIK |
Alright thank you I will see to that |
@puckpuck what do we do with respect to this comment? |
We should pause to let people return from Kubecon EU and read up on this thread. It doesn't hurt to have mulitle services in different languages talking to a database, but I want to make sure those efforts are coordinated properly. |
Alright thanks sir |
From SIG meeting discussion yesterday, the |
Feature Request
Hello Team.
I've been playing a bit with OpenTelemetry demo and started to think if there is any specific reason why we don't have any database instance (apart from Feature Flag Store)? I believe the easiest way to introduce it would be to create new service which reads orders from queue (Kafka) and save them to Database (e.g. MySQL or MongoDB). Then there could be some additional function added to Accounting Service which reads data from DB and perform some calculation. This additional feature would create additional capabilities to emphasise how great project OpenTelemetry is.
What do you think about this idea?
The text was updated successfully, but these errors were encountered: