model for a modern data access layer?
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
So, I take it from this that you're a principal consultant at a consulting firm, and that you want us to do your job for you. It's your job to write this proposal, not ours - after all, it's not as though you're going to pay us for something that's quite a substantial bit of work. What is clear from your description is that you don't understand how these patterns fit together - and if you don't, how are you going to be able to justify the different parts of your design when you're challenged by the client.
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
I see that you was able to climb really hi in the last 3 years - until 3 years before all your questions were mediocre at the best... If you got a principal consultant job by telling stories, you are in grate danger. Even someone should answer your question (no to likely, as it an article long answer), you will not understand and will not be able to present it, specially if questions will rise! So if you do not know your job it's better move along before some dirt will stick to your name...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
Member 3919049 wrote:
Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table.
In my experience of such people they charge a lot and produce very little. Judging from your question you are well suited to the role.
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
Member 3919049 wrote:
Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
No Problem. We sell workshops that result in a concept for this. You can buy one if you like. I bet there are some other consultants ready to be payed here, too. :rolleyes:
SharePoint Consultant and Developer at acocon Author of Primary ROleplaying SysTem I'm the ninth in a row of seven!
-
Hello, can you please describe a data access model for a modern, greenfield enterprise app? Back in 2000, a Bll and Dal were created for each domain entity. Business logic was in the Bll and data access logic was in the Dal. App code would instantiate a Bll and call one of its methods which would in turn instantiate and call a method on a related Dal. This is a proven and effective model and is still a solid fundamental model for basic applications. However, over the last 5 years, there has been increasing emphasis on design patterns like the provider pattern, inversion of control and a general emphasis on testability. So based on all the trends that have emerged, or become more recognized or expected over the last 5 years, can you please describe the data access model that you would propose for a modern, greenfield enterprise app? Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal.
