If you're open to it, I'm curious about a few things: 1. How do you handle DB interactions? A data mapper/repository pattern? 2. Do you have a service layer t

If you're open to it, I'm curious about a few things: 1. How do you handle DB interactions? A data mapper/repository pattern? 2. Do you have a service layer to coordinate between the different "inputs" (the REST API, event processing, and scheduled jobs) 3. Is this REST API used by a web front end or other services? Interested in how people handle token auth and/or using session tokens. I've been reading about architecture patterns more and I've realized which patterns I've used without knowing it, so now I'm interested in how others handle similar situations in different languages and ecosystems.