If you pay any attention to software technology trends at all,
there is no way you can have missed the “microservices”
architecture approach, which seems to be the cure to every
problem anyone ever had. But (Micro-)services, bounded contexts,
components, modules, classes, structs and records, procedures
and functions – whatever structuring mechanism we’re talking
about, a recurring challenge is to find the right size for
things. In this session, we will look at opposing forces from
both technical and organizational perspectives, and come up with
strategies for finding a good balance between the number of
things (in this case, microservices) and their size.
