#iddd

This user posted the following creation on Twitter (or X, whatever) for the International Dana Delany Day, and I am literally obsessed

Also feeling sappy tonight because I’m only NINE followers away from 150!!! This is such a huge milestone for me, when I started this account I did it purely for my own enjoyment, and it’s so cool that ANYONE wants to read my work!! Thank you all from the bottom of my heart❤️ I’m going to do a couple more chapters of Buzzcut before putting it on mini hiatus (tbh probably not much longer than how long I normally take to post) where I’m going to write more of my other pairings (senator x Obi, revisiting my IDDD fic) rest assured buzzcut fans, I’ll have plenty more chapters after hiatus and probably 2 more before!! Also, please feel free to send requests! I write for y’all!!!

Chynna - iddd (Video)

A Service in the domain is welcome to use Repositories as needed, but accessing Repositories from an Aggregate instance is not a recommended practice.

Is Separated Interface a Necessity? Since this AuthenticationService does not have a technical implementation, is it really necessary to create a Separated Interface and implementation class, and in separate Layers and Modules? No, it is not, in fact, an absolute necessity. We could have created this particular Service with only a single implementation class with the name of the Service: ... There would be nothing wrong with this. You might even consider this a more fitting approach since this particular Service may never need to have multiple implementations. However, given that different tenants might eventually desire specialized security standards, it's possible that there could be multiple implementations. At this point in time, however, the team has decided to drop the use of a Separated Interface and go with the class as shown here.