How Mendz.Data.* Can Simplify Your Apps
The idea and motivation behind Mendz.Data is to remove the abstraction out of project planning, so that you can jump right ahead to coding and development. Mendz.Data is not just a library of APIs. As advertised, it is designed to provide tools and guidance.
As with other libraries, Mendz.Data.* is provided with assumptions. Assuming that you are willing to create contexts that are semi-self-initializing without requiring .Net's DI mechanisms, you can use IDbDataContext and its implementations. Assuming you are willing to create "repositories" that implement only the CRUDS methods that a POCO needs, you can use the interfaces in Mendz.Data.Repository(.Async) as your guide.
Most of the time, developing applications means coding routine constructs. Templates can be created out of the Mendz.Data.* APIs. These templates can be re-used every time you'll need to create a new context or a new repository. Templates help speed up coding for most similar requirements. With well tested codes in place, consistency and quality can be easily achieved. Copy-paste is not all that bad... you know what I mean. IMHO, at the end of the day, it matters that you spent more time testing your work than coding them.
Your coding/project templates can mature as your application matures. Because these templates are developed by you, you can keep them up to date. Visit Mendz.Data wiki, or Mendz.Data.SqlServer wiki, or Mendz.Data.MongoDB wiki for samples that you can base your templates on.
As with other libraries, Mendz.Data.* is provided with assumptions. Assuming that you are willing to create contexts that are semi-self-initializing without requiring .Net's DI mechanisms, you can use IDbDataContext and its implementations. Assuming you are willing to create "repositories" that implement only the CRUDS methods that a POCO needs, you can use the interfaces in Mendz.Data.Repository(.Async) as your guide.
Most of the time, developing applications means coding routine constructs. Templates can be created out of the Mendz.Data.* APIs. These templates can be re-used every time you'll need to create a new context or a new repository. Templates help speed up coding for most similar requirements. With well tested codes in place, consistency and quality can be easily achieved. Copy-paste is not all that bad... you know what I mean. IMHO, at the end of the day, it matters that you spent more time testing your work than coding them.
Your coding/project templates can mature as your application matures. Because these templates are developed by you, you can keep them up to date. Visit Mendz.Data wiki, or Mendz.Data.SqlServer wiki, or Mendz.Data.MongoDB wiki for samples that you can base your templates on.
Comments
Post a Comment