Microservice, Monolith, and Serverless are some of the three architectural styles that have recently gained popularity. Some engineers swear one over the others, but in reality, there is no black and white: there are advantages and disadvantages, depending on each use case. For example, if the flow of your services are dependent one another and each service doesn’t need to scale independently, is it worth increasing the development power it needs to maintain infrastructure?

This talk is designed to provide the pros and cons of going one way versus another, providing real life examples of how things didn’t work out when architectural decisions weren’t vetted deep enough. Hopefully, by the end of this talk engineers and business alike will be able to have initial conversations on the route they’d like to take on their next project.