A category $\mathcal{C}$ consists of a collection of objects, denoted $\text{Obj}(\mathcal{C})$ and, for every two objects $A, B \in \text{Obj}(\mathcal{C})$, a set of morphisms $\text{Hom}(A,B)$, also called homsets, satisfying the following properties:

For every three objects $A,B,C \in \text{Obj}(\mathcal{C})$, there exist a binary operation $\circ$, called composition of morphisms, that satisfies the composition law:
 $\circ : \text{Hom}(B,C) \times \text{Hom}(A,B) \rightarrow \text{Hom}(A,C)$, that can be written as: $(g,f) \rightarrow g\ \circ\ f$

Composition is associative: for all $A,B,C,D \in \text{Obj}(\mathcal{C}), f \in \text{Hom}(B,C)$, $g \in \text{Hom}(A,B)$, $h \in \text{Hom}(D,A)$ we have:
 $f \circ (g \circ h) = (f \circ g) \circ h$

For each $A \in \text{Obj}(\mathcal{C})$, there is a unique element $1_{A} \in \text{Hom}(A,A)$ (identity morphism), such that, for every $B \in \text{Obj}(\mathcal{C})$, we have left and right unit laws:
 $f \circ 1_{A} = f$ for all $f \in \text{Hom}(A, B)$
 $1_{A} \circ f = f$ for all $f \in \text{Hom}(B,A)$
It is common to express $A \in \mathcal{C}$ instead of $A \in \text{Obj}(\mathcal{C})$ and when indicating $f$ is a function from $A$ to $B$, it’s typically written as $f: A \rightarrow B$ rather than $f \in \text{Hom}(A,B)$.
A category is a very general concept, the objects and morphisms can be anything, as long as they adhere to the stated conditions. The following is an example category with a collection of objects $A, B, C$ and collection of morphisms denoted $f, g, g \circ f$, and the loops are the identity morphisms.
\begin{xy} \xymatrix{ A \ar@(l,u)^{1_A}[] \ar_{g\ \circ\ f}[dr] \ar^f[r] & B \ar@(u,r)^{1_B}[] \ar^g[d]\\ &C \ar@(d,r)_{1_C}[] } \end{xy}One interesting aspect that follows from the left and right unit laws is that the identity morphism is unique, so there really is just one way to loop back to itself.
Proposition. The identity morphism is unique.
Proof. Suppose that each of $1_{A}$ and $1'_{A}$ is an identity morphism. Then by left and right unit laws we have: $1'_{A} \circ 1_{A} = 1'_{A}$ and $1'_{A} \circ 1_{A} = 1_{A}$, hence $1'_{A} = 1'_{A} \circ 1_{A} = 1_{A}$
$\pmb{\scriptstyle \square}$
In Coq.
Example
In Haskell, Category is a type class that abstracts the concept of a mathematical category. In the context of Haskell, types are considered as objects and functions as morphisms.
In Haskell, one traditionally works in the category (>) called Hask, in which any Haskell type is an object and functions are morphisms. We can implement Hask as follows:
As we can see, cat
has simply been replaced by Haskell arrows. The id
function is the identity morphism that leaves the object unchanged. The (.)
function is a composition of morphisms, which obey category laws in pseudo notation:
Haskell faces some challenges when considered in its entirety as category Hask due to features like nontermination and bottom values. Therefore, when speaking about Hask it is often referred to a constrained subset of Haskell that excludes these problematic aspects. Specifically, this subset only permits terminating functions operating on finite values. It also resolves other subtleties. In essence, this pragmatic subset removes everything preventing Haskell from being modeled as a category.
The Category typeclass^{[1]} can also be used with other structures that can be viewed as categories, not just functions between types. For example, it can be used with the Kleisli category of a monad, where morphisms are functions of type a > m b
. The objects in this category are identical to the types in Haskell as found in Hask
. However, the transformation between these entities are represented by Kleisli arrows.
Kleisli arrows are a way of composing monadic programs. They are a notational feature that can be useful, but they don’t provide any additional functionality beyond what the monad already provides. The use of this syntax in Haskell, since it overwrites id
and standard function composition (.)
, can be quite confusing if used in this manner. Instead, Kleisli composition is often defined using the “fish” operator, as shown below:
As we can see <=< can be expressed in terms of >>=
and vice versa, hence they form an isomorphism. All of the above is already implemented in the standard Haskell library, so you can simply open an interactive Haskell interpreter (ghci) and test the following examples:
Here are some more examples:
 $\mathbf{Set}$, the category of sets and set functions
 $\mathbf{Mon}$, the category of monoids and monoid morphisms
 $\mathbf{Grp}$, the category of groups and group morphisms
 $\mathbf{Rng}$, the category of rings and ring morphisms
 $\mathbf{Grph}$, the category of graphs and graph morphisms
 $\mathbf{Top}$, the category of topological spaces and continuous maps
 $\mathbf{Preord}$, the category of preorders and order preserving maps
 $\mathbf{CPO}$, the category of complete partial orders and continuous functions
 $\mathbf{Cat}$, the category of categories and functors
 Monoids are themselves oneobject categories
 The category of data types and functions on data structures
 The category of functions and data flows (data flow diagram)
 The category of stateful objects and dependencies (object diagram)
 The category of values and value constructors
 The category of states and messages (state diagram)
References
 0.The diagram displayed at the top of this post is a modified version of Brent Yorgey's Typeclassopedia diagram ↩
 1.Control.Category ↩