Friday, February 26, 2010

PLINQO aka Professional LINQ to Objects rules!

I was looking for a couple of days of how to upgrade to web 2.0 applications by using the last new technologies such as ExtJS, ASP.NET MVC, WCF and others.
All good regarding the new technologies, but suddenly I realize that while I'm upgrading the front-end to web 2.0, I'm still getting stuck to the old back-end!

I personally hate Linq-To-SQL because of its buggy limitations, and the ease of making things go slow. On the other hand I do love the LINQ by its design.
Same problem like three years ago in 2007 when I ended up to write my own generator because at that time CodeSmith was too limited for my needs.
Now, I hate my generator too, because it works too slow and I don't have enough time to upgrade my designs. I also hate NHibernate, because I don't want to learn dying technologies like HQL.
I also don't understand the purposes of other languages than javascript /:) (well, kidding, but that is true). Of course javascript lacks of several features from other languages i.e. LINQ :) but that's another story I'm gonna share later on.

After two days of investigating a dozen of brand new technologies, I came across over a few back-end solutions, all looking promising, but none of them more than PLINQO!

How do you feel, if you can still use the LINQ concept and don't care about all of its past issues that were on the standard Linq-to-Sql design? (some would say LinQ to StinQ design, yeah it stinks l-))
Well, you still care about them, but now you have quick and nice ways of dealing with them without all the painstaking work and the missing of the bits and pieces.

Too many talking!
Let's get to the facts.

I'm not going to describe each and every advantage of the PLINQO features, as you can read about them right here.

However, there are a few that caught my eye and I would like to get a short brief about them.
  • Entities, especially Serialization / Deserialization of entities.
  • Oh yeah, Caching :-> although I'm not yet convinced about if it has support for SqlCacheDependency support for SQL Server 2008 features
  • Futures also known as batch grouping.

  • Batch updates & deletes
  • Many to many relationships - I hate that third table too, now it's gone!
  • Rules

  • Enums
  • Linq-To-SQL Profiler

... and a lot more :)

I loved this article about LinQ-to-StinQ :) ! Well, not anymore with PLINQO!
I will get back in a few weeks, when I get a project in production with more discoveries and impressions.

The whole idea with PLINQ is that you can generate the entities in a few seconds and use them whatever you like, on the fly with the power of LINQ.

Happy generating!
Blog powered up by Blogger