views:

62

answers:

3

The subject of this question speaks for itself. I am wondering if Fluent NHibernate is ready for production code. I am especially wondering in light of some seemingly simple problems that I am having with it that I haven't yet found fully satisfactory solutions for (and the community doesn't have a solution for?)

Why is Fluent NHibernate ignoring my convention?

Why is Fluent NHibernate ignorning my unique constraint on a component?

Yes, I am aware of this old question which is more than a year old; the answer seems to be kinda-sorta-maybe.

Is Fluent NHibernate is ready for production now?

+1  A: 

This kind of question really should be asked over on their google group page: http://groups.google.com/group/fluent-nhibernate. Being an open source project that is constantly evolving with NHibernate itself, it will almost always be in a semi-flux state, especially with NH3 coming soon.

Chris Conway
+4  A: 

By what metric do you measure "production ready"? How is production any more stringent than other environments? Only you can decide if it meets your needs.

Your first question you have a work around for. Fluent NHibernate is open source, if people aren't dying because of a bug (aka, there's a work around available), it's unlikely our finite resources will be spent on it when there are more important things to be working on. Enums are a known issue, primarily because 50% of people expect them to be mapped as ints, and the others expect strings; either way, one party is going to think that the implementation is a bug.

Your second question looks like a bug. Funnily enough, the Fluent NHibernate developers don't trawl Stack Overflow for possible bugs. If you don't tell us that a bug exists, we won't be able to fix it; sadly, I'm not psychic.

Fluent NHibernate has is past 1.0, which is quite a significant milestone for an OSS project, and is in use in hundreds of production applications. Whether that makes it "production ready" can only be decided by you.

If you don't think it's production ready yet, it's open source and we're always looking for contributors.

James Gregory
@James Gregory: Thanks for your thoughts. I'm starting a new project and this is my first time using FNH. I love the idea of it, and would prefer it over non-FNH. But very early on I've already run into two problems. I am trying to get a sense if should I expect many more problems as I get deeper into the project and thus should abandon it or if I should stick with it over these bumps. It's not whether or not I think it's production ready; I don't have enough experience with it to judge that. I sense a little defensiveness in your post and I'm sorry if something in my question led to that.
Jason
Sorry if I came across as a little defensive, I was defending my womans honor. Open Source projects, like most other software projects, are rarely bug free or complete; as is often said, 90% of the project takes 90% of the time, and the last 10% takes another 90% of the time (and that's when the developers are getting paid for it!). Fluent NHibernate is stable, established, and fairly well maintained; it does have bugs and issues, but I don't think there are any showstoppers (and if there are, we'll get them fixed).
James Gregory
Oh, and I was being serious about looking for contributors ;)
James Gregory
@James Gregory: No problem; I truly the respect the work you've done and think FNH is a wonderful idea. I've decided to stick with it through this project.
Jason
@James Gregory: And I'll take a look at the `Unique` problem; should be fun. :-)
Jason
A: 

Do you have unit tests that cover the scope of the functionality of your interaction with Fluent NHibernate? If you do, and they work, then why worry about other features that don't work that you don't use. Besides, a lot of issues with any open source project is lack of understanding of how to use it.

Rich

related questions