dockerkubernetesmicroservicesmonolithicnon-web

Design and architecture solutions to break a monolithic "NON web based local host application"


I am looking at pointers for design and architecture solutions to break a monolithic application. This application is a non-web, localhost application. How can I do this using Microservices, Kubernetes, Dockers? Are Dockers, Kubernetes and Microservices design patterns only applicable to Web-based apps?


Solution

  • Here is a good starting point describing patterns for refactoring monolith app to microservices.

    It also contains two examples there with the same application: one being the monolithic and the same microservices based one so that you can see how exactly it was refactored into small pieces.