AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Microcosm database4/27/2023 In fact, moving off of the (usually costly) enterprise relational database is one of the benefits often promoted for refactoring to microservices. What’s more, there’s a nearly even chance that this database is an Oracle database-all the rest of the relational databases (DB2, SQL Server, Informix, or even an open source database like MySQL or Postgres) split the remainder of the share. If your application is like most of the applications that we see that are starting down the road to be refactored into microservices, we can probably safely assume that it’s working with a single, large relational database. Starting slow: One big database or many little databases? But first, we need to address what is often the initial question asked by teams refactoring existing enterprise applications into microservices. We’ll look at several of these cases and talk about data modeling choices you can make to simplify and improve your refactored code. What we have seen is that, sometimes, it’s hard to determine when you are looking at a coding issue or a data modeling issue that is masquerading as a coding issue. One of the last aspects we touched upon was the question of what to do with your data-in large-scale enterprise applications, that is often the thorniest issue and one that is worth a more in-depth treatment. In a prior article, we touched upon a few of the different aspects that can lead you to refactor your code to a microservices-based approach. Exploring the different factors to consider while trying to determine the best database options when refactoring to a microservices approach.
0 Comments
Read More
Leave a Reply. |