Not many developers are familiar with the concept of DSLs (Domain Specific Languages) even fewer use them in their day job. It seems that creating a new language is a hard job that should only be left for professors in the academia or certain employees that work in Microsoft, Sun or some other compiler vendor.
But not all languages are created equal in the world of DSLs, there is a branch of languages called “Internal DSLs” – that any developer worth his salt can leverage to create better, more readable code.
Internal DSLs and fluent interfaces
The basic idea of a domain specific language (DSL) is a computer language that’s targeted to a particular kind of problem, rather than a general purpose language that’s aimed at any kind of software problem. Domain specific languages have been talked about, and used for almost as long as computing has been done.
Martin Fowler – DomainSpecificLanguage
And so internal DSL (a.k.a “Embedded DSL) is a domain specific language created using an existing (host) language.
Within the group of internal DSLs there is sub group known as “fluent interfaces” – basically using the host language to create code that can be easily read – and look (after a fashion) just like plain English.
The term “Fluent Interfaces” was coined by Eric Evens and Martin Fowler and it refers to an implementation of object oriented API on top of existing functionality in order to provider more readable code.
Why should you care?
There are many benefits of using fluent interfaces – you can create a easy to use and understand API that does not require any additional libraries to implement.
That API provides directions on how the code should be used and can help your users use your software or you can use it internally in order to make a complicated process easy to code by your teammates.
There is one catch – creating a good API is always difficult and creating fluent interface requires understanding of certain tricks in the language that can be leveraged to create the desired code.
C# just like any other object oriented language has the capability to create fluent API in fact certain feature of C# makes it extremely easy to create such API.
In the upcoming posts I’m going to show a few tricks that I’ve used in the past to create fluent interfaces all of which you probably already know.
So until next time – happy coding…
3 thoughts on “Fluent Interfaces in C#–Introduction”
I guess it is worth to discuss the pro's and con's in comparison to non-fluent APIs (object initializers, basically).
Seems like a very “religious” debate – also “it depends” on the API in question.
Pro's and con's are never religious. Deciding on the relative weight is.