I'm working on a system with some basic CRUD services handling domain objects like users and posts, saving them directly to the database without any transformation. Now, I've hit a point of confusion with more complex services, like one for signing up users. Should I keep the sign-up functionality as a standalone service, or is it better to cluster it with other complex services? I'm considering whether to group it under something like AuthServices, but that feels out of place domain-wise. I'd appreciate any insights!
5 Answers
Just a heads-up: persistently changing data (like adding a user) is a side effect! You might want to explore functional programming for better isolation from side effects. Depending on your architecture, it can help shape the way your services interact. Ask yourself whether you need sign-up to be universally accessible or if it can be confined to certain areas of your app.
The classification of your services can vary greatly. Some folks prefer to implement one service per business function, while others might combine related services. Since you're dealing with CRUD, think of those as repositories. Just remember, there’s no perfect way to do it. It might help to keep your services flexible and allow for easier composition, especially if your language supports functional programming!
I appreciate that there's no right answer; it's just what I needed to hear!
When structuring your services, focus on data ownership. For example, if you have a user service, the sign-up process should ideally live there to keep things straightforward. Each service should handle its own data, creating a clear ownership boundary. This way, you avoid a tangled mess of service calls.
What do you mean by 'data ownership'? I get that it ties into separation of concerns.
Adopting a modular approach as a starting point can work wonders. Once you've identified the right balance between modules without circular dependencies, you can split them into standalone services if necessary. This helps isolate functionalities while allowing for growth.
I'm already doing the modular thing! My confusion was about where to put signUp functionality.
I'd recommend separating the sign-up user functionality into its own service. It allows you to manage user data directly while AuthService can handle the authentication side. It’s a cleaner approach and prevents your service logic from becoming too intertwined.
That sounds like the path I’ll take!
That's a good point! Why is 'currentUser()' accessible everywhere though?