Another source: Microservices Pattern: Database per service | | | | | |
| | | | | Microservices Pattern: Database per service A service's database is private to that service | | | Sergey Prokhorenko [email protected] On Friday, 22 March 2024 at 04:58:59 pm GMT+3, Sergey Prokhorenko <[email protected]> wrote: BTW: Each microservice should have its own database to ensure data isolation and independence, enabling better scalability and fault tolerance Source: Microservices Pattern: Shared database | | | | Microservices Pattern: Shared database | | | | | | | Microservices Pattern: Shared database | | | Sergey Prokhorenko [email protected] On Friday, 22 March 2024 at 04:42:20 pm GMT+3, Sergey Prokhorenko <[email protected]> wrote: Why not use a single UUID generator for the database table in this case, similar to autoincrement? Sergey Prokhorenko [email protected] On Friday, 22 March 2024 at 03:51:20 pm GMT+3, Peter Eisentraut <[email protected]> wrote: On 21.03.24 16:21, Jelte Fennema-Nio wrote: > On Wed, 20 Mar 2024 at 19:08, Andrey M. Borodin <[email protected]> wrote: >> Timer-based bits contribute to global sortability. But the real timers we >> have are not even millisecond adjusted. We can hope for ~few ms variation in >> one datacenter or in presence of atomic clocks. > > I think the main benefit of using microseconds would not be > sortability between servers, but sortability between backends. There is that, and there are also multiple backend workers for one session.
