Giter VIP home page Giter VIP logo

Comments (1)

iammukeshm avatar iammukeshm commented on May 18, 2024

Hi, Thanks a lot for the feedback :D Here is my take. My Opinion :P

  1. In theory, this was placed as interface/implementation to accommodate various DateTime logics during test cases. It would not always be DateTime.Now right? Test cases can be run for multiple time factors with this approach.

  2. I believe Repo Pattern creates an abstraction over the DataAccess Tech. 2 Years ahead and if EFCore is no longer the best ORM, it should be pretty simple to integrate/switch to a better ORM with less coding.

  3. Again, IEmailService is just an interface. There are n ways to send out emails like direct SMTP, mail relays, SendGrid, or basically any other provider. The core aim of the interface is to have different implementation at the infrastructure level. As of now, only SMTP is implemented. But it is very easy to have a Sendgrid Implementation too.

  4. Behavior pattern is something that i came across while working with mediatR library. Found this usage in several Microsoft Projects too. Retuning EXC from the BL may be good, but to have centralized control, I felt it better to be in the APP layer. So that different implementations won't hurt the message formats. Also, I had globalization concerns in my mind regarding error messages.

  5. Yes, Technically they are already in the Common Library. With correspondence to the app setup, Application/Core acts mostly as the common library for the Enterprise/Application. I wouldn't have a different DLL just to accommodate these response classes because the response is something that is very specific to a business. Making it a nugget package / separate project may not be re-usable always. So, don't you think it is better to maintain response classes specific to an application?

  6. Same answer as above.

  7. Yep, that's a cool idea. Might be overkill at this stage of the project. I Will put that to my list.

  8. Again, Settings is something common and core to the project. I wouldn't put them to the infrastructure with this kind of arch setup.

from cleanarchitecture.webapi.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.