Book Image

F# 4.0 Design Patterns

By : Gene Belitski
Book Image

F# 4.0 Design Patterns

By: Gene Belitski

Overview of this book

Following design patterns is a well-known approach to writing better programs that captures and reuses high-level abstractions that are common in many applications. This book will encourage you to develop an idiomatic F# coding skillset by fully embracing the functional-first F# paradigm. It will also help you harness this powerful instrument to write succinct, bug-free, and cross-platform code. F# 4.0 Design Patterns will start off by helping you develop a functional way of thinking. We will show you how beneficial the functional-first paradigm is and how to use it to get the optimum results. The book will help you acquire the practical knowledge of the main functional design patterns, the relationship of which with the traditional Gang of Four set is not straightforward. We will take you through pattern matching, immutable data types, and sequences in F#. We will also uncover advanced functional patterns, look at polymorphic functions, typical data crunching techniques, adjusting code through augmentation, and generalization. Lastly, we will take a look at the advanced techniques to equip you with everything you need to write flawless code.
Table of Contents (20 chapters)
F# 4.0 Design Patterns
Credits
About the Author
Acknowledgements
About the Reviewer
www.PacktPub.com
Preface

Addressing run-time problems


The mantra "if it compiles, it works" helps followers score amazingly well in time-to-market ratings for enterprise software development.

Taking Jet.com as an example of building green field e-commerce platform implementation, it has really condensed the path from zero to minimum viable product (MVP) in less than a year. Release of the platform to the production mode took place in a bit more than a year from the reception.

Does this mean following a functional-first approach is a software development silver bullet? Surely not on an absolute scale, although on a relative scale, the improvements are just great.

Why is the success not exhaustive? The thing is that the practice requires transition from gory ideas to mundane implementation issues. No matter how accurate our implementations are, there are always dark corners exist where unexpected problems may lurk.

Let me demonstrate this with a sample taken from F# enterprise development practice at Jet.com. Jet represents...