I ran into a versioning problem when I tried to use the latest version of FluentNHibernate with the latest version of LINQ to NHibernate because LINQ to NHibernate is built using a later version of the NHibernate binaries.
After doing a little search, I found a version of NHibernate which both LINQ to NHibernate and FluentNHibernate had been built against here.
So now, I can enjoy the same fluent interface to configure NHibernate and the use of LINQ query like this:
var onePiece = from s in session.Linq<Series>() where s.Name == "One Piece" select s;
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong