How to Namespace APIs to Avoid Naming Conflicts

It's a way to organize a set of endpoints and APIs together, but it's doing it for a different reason. Imagine another use case might be that you maybe want to organize things by something more related to the business domain. And so from the adapter, it looks like it's more about adapting for a specific kind of client, like a device or a web versus with the lens. It's kind of an adapter as well. So similar to the adapter, but kind of with a different purpose, I guess. Okay. Now how about API names spacing? Yeah. That's something very early on when I started experimenting with the idea of treating APIs like dependencies. What we actually need