- Paperback: 312 pages
- Publisher: Pragmatic Bookshelf; 1 edition (Feb. 4 2018)
- Language: English
- ISBN-10: 1680502549
- ISBN-13: 978-1680502541
- Product Dimensions: 19 x 2.5 x 23.5 cm
- Shipping Weight: 549 g
- Average Customer Review: Be the first to review this item
- Amazon Bestsellers Rank: #68,604 in Books (See Top 100 in Books)
Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F# Paperback – Feb 4 2018
|New from||Used from|
Customers who bought this item also bought
About the Author
Scott Wlaschin is an expert on F#, author of the popular F# site fsharpforfunandprofit.com, and a board member of the F# Software Foundation. Known for his non-academic approach to functional programming, Scott is a popular speaker and has given talks at NDC, F# Exchange, DDD Europe, and other conferences around the world.
|5 star (0%)|
|4 star (0%)|
|3 star (0%)|
|2 star (0%)|
|1 star (0%)|
Most helpful customer reviews on Amazon.com
I had trouble imagining how you could scale F# to a larger "business" project. Very clear descriptions.
The entire book follows a project from design -> implementation using F#. The project is not too simple.
The whole approach really opened my eyes, and I'd like to try something like this on my next project.
People trying to learn Haskell might want to read this book as a more pragmatic and less academic introduction to topics like monads, functors, applicatives (etc.). Scott's ROP (railway oriented programming) nicely motivates Haskell style either monads.
The use of type providers for accessing a database is nicely described in this book: type providers are a realization of the Scheme (MIT's dialect of LISP) principle of first class citizens, because type providers lift disparate data sources to first class status that can be statically type checked at IDE and compile time. (F# is the only language I know of that has type providers.)
I hope Scott will provide a print version of his world famous "F# for Fun and Profit" materials (which nicely dovetail with this book). I also hope other authors will step in to provide more backdrop on questions this book is likely to raise (especially for those coming from an OOP background). For instance, is there still a place for micro ORMs? Why or why not? Also, guidelines for people porting C# code that uses ORMs to F# (and other functional languages). What incremental steps can be leveraged to advantage (to avoid wholesale replacement costs)?
Awesome book that rocked my world. Highly recommended.