Hi! I quite don't understand what you mean.
Is your question about making each micro service only have its own database that is not shared with other micro services? In my opinion this is doable and worth further discussion. Or do you have a need to use other database vendors besides Postgres. If this is the case then my answer is that we have limited resources and if we would support different database vendors it would consume too much of the limited development resources we have at hand. Kind regards Juhan Kontakt Saransh Sharma (<sara...@muellners.org>) kirjutas kuupäeval L, 27. juuni 2020 kell 19:54: > Hey Juhan , if you are reading this email.. I am looking to understand how > to make CN services more agnostic by providing more services config on > hand, as I see right now it's configured to have only postgres. > > So essentially it's tied to postgres then (are we suggesting that we only > use postgres). > > This can become problematic actually why ? because we cannot add more DB > support to standalone isolated env. > > We are trying to have isolated services with individual service support of > DB and externally services connected to each service. This way we could add > independent services made out of any language and any DB. > > Let me know your thoughts. > > > -- > Thanks and regards, > > Saransh Sharma > Research Partner > > This mail is governed by Muellners® IT policy. > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents > of this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. >