Welcome to the Linux Foundation Forum!

Rewriting legacy CRUD applications

Options

Chapter 4 talks a lot about rewriting legacy applications in order to decouple them and make them transient. To this end, my team has a few apis which are essentially just database abstraction layers (i.e. there's a 'user' table in the db and a 'User' package in the api which allows basic CRUD operations on the table)

I was wondering what people's thoughts are on the best approach to optimizing an application like this for Kubernetes. Would you simply split each package up into its own microservice (i.e. UserMicroservice, InvoiceMicroservice, etc...), or are there other considerations I perhaps need to take into account?

Categories

Upcoming Training