Architecture

  • image
    A system typically has use cases requiring coordination between multiple services. When selling a product, for example, an ecommerce site may use several services to bill, deliver to, and communicate with the client. This post discusses a possible way to execute this type of use case.
  • image
    On a previous post we defined software architecture as a set of rules for defining the components of a system, and for how those components interact with each other. Now we explore why software architecture can influence how a system evolves over time impacting its maintainability.
  • image
    Microservices and monoliths are often presented as polar opposites. But microservices, monoliths and everything in between are attempting to solve the same problem: how best to write software? Software architecture describes what answers to this question share in common.