About ORM Running points

Also see ORM run points, to tell the truth, this ORM run points meaningful? But also the crowd, like to see the lively people are really a lot of ah.

Often see a lot of people, in blowing an ORM performance how, how good, and then supplemented by a few unit test run points to support, and our heavenly mobile phones boast good performance, the price is cheap what are the two? Even a mobile phone is not comparable to, at least, mobile phone, still dare to collect money!

As we all know, the simple measurement of a mobile phone is good or bad, not only the performance, but also the screen, heat, workmanship, service and so on. Again, the measure of an ORM is not just the performance. In fact, the performance of ORM, the impact on the entire system is very small, the real head is in IO that piece, and the gap is geometric level. If an ORM is not good, you need to check the database, no matter how you optimize the algorithm, the overall query time is greater than the less than one time Orm.

To measure an ORM, it should also include:

1, ease of use, must be within 10 minutes to enable users to start.

2, stability, can withstand the verification of time.

3, with a strong query function, including Linq query, ESQL query.

4, in line with the standards set by Microsoft. Because we are using Microsoft's products, in line with Microsoft's standards, not only can make the product more general, and can reduce the cost of learning users.

It can be said that the use of ORM people are not too concerned about performance, they are looking for an ORM enough to be able to shorten the product development cycle as far as possible, as long as the performance is not bad enough to accept. At the very least, I've never heard of a user complaining about poor performance in Alinq. Care about performance, is not using ORM, what to use? Stored Procedures! In fact, many large software uses ORM + stored procedures.

Now the CPU is not performance is insufficient, but the performance is excessive, so you can see the current CPU research and development direction, not performance-oriented, but emphasis on energy consumption ratio. In the mobile phone CPU is 4 nuclear popularization, towards the 8 core today, for ORM, still need to obsess about performance? The real big head is in IO.

If you really want to do products, you should go down to the heart to do research, with your products, services to impress your users, have a good product, then publicity will have a good effect. Rely on a number of gimmicks to attract users, is no use, customers are not stupid, no good products as a support, will allow users to abandon, and no word of mouth, in the community mix, Word-of-mouth is your brand.

Many friends, have asked me, now so many open source free orm, why they do not use EF, NH so free open source and use your alinq?

First, the service is thoughtful. With EF, NH, is there a problem, can you find the author to ask? With Alinq, as long as you are willing to pay, midnight call me up also does not matter.

Second, the product is convenient, easy to start, stable performance. Interested can download, take a look at the document, try it, I promise you will like it immediately.

Third, there is always a little money for the company, thousands of dollars, that is, to make a report to apply for things.

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/