Best practices for Telerik Data Services Wizard + OpenAccess

3 posts, 1 answers
  1. Seree
    Seree avatar
    29 posts
    Member since:
    Sep 2006

    Posted 31 Mar 2010 Link to this post

    Hi,

    First of all, thanks for such a great ORM product that seems very friendly to developer. :)

    I have read the ORM Made Easy courseware and found that the N-Tier example is providing a good practices to build an Enterprise grade application. (contains Data later, Business layer and Service layer)

    However, when I read the Telerik Data Services Wizard on Getting Started document, I am a bit confuse with what DSW provides.

    From the ORM Made Easy courseware, I saw that the Service layer should generate on top of the Business layer. (Which Business layer contains "Manager" or "Repository" classes)

    But I found that the DSW try to generate a Service layer on top of Entities which is Data layer.

    So, I just wonder what is the primary objective for DSW? as DSW can not expose Business layer to Service layer.

    This seems it is useless to me as I always want to generate a Service layer from Business layer and not from the Data layer like what DSW did.

    I am sorry but I just confuse about the DSW by now and have following questions.
    1. What is the best practice to build an Enterprise grade application architecture with OA + DSW?
    2. What is the primary objective for DSW? (generate CRUD for Entities and expose it as a Service?)
    3. I need to code my own Business layer on top of the generated CRUD Service and make another Service layer which will be connected to Presentation layer myself right?

    Looking forward to hear from you. :)

    Best regards,
    Seree W.
  2. Answer
    Damyan Bogoev
    Admin
    Damyan Bogoev avatar
    581 posts

    Posted 01 Apr 2010 Link to this post

    Hi Seree,

    1.   Currently it is not possible to use business objects on top of the data layer with the Data Services Wizard. If you generate the services via the Data Services Wizard you will have to work directly with the entity objects. We are planning to provide a mechanism for generating business objects based on the persistent classes (and the DSW should be able to create services for them) but this would not be earlier than Q2 2010. In the meantime you will have either to use the DAL objects directly with the service or implement the service and business objects manually as shown in the N-Tier example.
    2.   Yes, this is correct. I also recommend you to have a look at the documentation for the DSW for better explanation of its capabilities and how to work with it.
    3.   Surely, this can be done. However I think that would be a bit of an overhead for the application. Since you are going to implement a service, with similar efforts you can implement this service to work with business objects and do the querying and translation from business to persistent objects (and vice versa) in the Business or DAL layer instead of calling a second service generated by the DSW. This is actually again the approach of the N-tier demo.
    To sum up, I would suggest you to use the DSW only if you are going to work with the persistent objects directly in the service. Otherwise, writing the service manually should be the better choice at this point.
    Hope that helps.

    Best wishes,
    Damyan Bogoev
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. DevCraft banner
  4. Seree
    Seree avatar
    29 posts
    Member since:
    Sep 2006

    Posted 01 Apr 2010 Link to this post

    Hi Damyan,

    Thanks for taking time to answer my questions. It really help me understanding the DSW and OA much better. :)

    I will keep in track with Q2 2010 release and it could be great if we can see DSW handle the Business objects. (At least generate a Service layer from it)

    Best regards,
    Seree W.
Back to Top