Book Image

Learning Functional Programming in Go

By : Lex Sheehan
Book Image

Learning Functional Programming in Go

By: Lex Sheehan

Overview of this book

Lex Sheehan begins slowly, using easy-to-understand illustrations and working Go code to teach core functional programming (FP) principles such as referential transparency, laziness, recursion, currying, and chaining continuations. This book is a tutorial for programmers looking to learn FP and apply it to write better code. Lex guides readers from basic techniques to advanced topics in a logical, concise, and clear progression. The book is divided into four modules. The first module explains the functional style of programming: pure functional programming, manipulating collections, and using higher-order functions. In the second module, you will learn design patterns that you can use to build FP-style applications. In the next module, you will learn FP techniques that you can use to improve your API signatures, increase performance, and build better cloud-native applications. The last module covers Category Theory, Functors, Monoids, Monads, Type classes and Generics. By the end of the book, you will be adept at building applications the FP way.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Application architectures


Four years ago, I posted an article entitled Application Architecture Considerations.

Consider the following diagram:

I had talked about things to consider when evaluating an application's architecture.

Note

For a list of things to consider when designing an application architecture, see http://lexsheehan.blogspot.com/2013/05/application-architecture-considerations.html.

Some of these things are listed as follows:

  • Functionality: Does the application satisfy its business requirements?
  • Performance: Does the application run fast enough? For example, if there are any views that take longer than 7 seconds to display, then you need to re-engineer something.
  • Scalability: How well does your application scale? Can you easily add and remove components without affecting your application's performance or reliability? How loosely (or tightly) coupled is your application code?

It was all high level, mainly discussing nonfunctional requirements and cross-cutting concerns, for example,...