faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
_whitelogger has joined #amber
_whitelogger has joined #amber
feepbot has quit [Ping timeout: 246 seconds]
feepbot has joined #amber
_whitelogger has joined #amber
<FromGitter> <damianham> I am planning for the future and considering the architecture of the backend APIs and databases. We will be developing a number of distinct services, each of which will have their own distinct set of database tables. I am most likely going to deploy the APIs on server clusters in distinct sub-domains for each service. Some of the database records in each service will be owned by a User and there will be one
<FromGitter> ... common user identity across all services. Should this grow to a very large user base we would need to ensure there are no bottlenecks with database access and I suppose the common approach would be to cluster the database and all services would use the same database cluster. An alternative would be to segregate the dat ... [https://gitter.im/amberframework/amber?at=6029569fe634904e609d2d14]
<FromGitter> <eliasjpr> Hello Damian, when I worked for Stash I was responsible the for user identity, authentication and authorization, and a Postgres database worked just fine with approx 5 million active users we also had a caching layer REDIS that offload the dB quite a bit