關於這本電子書
Domain-Driven Design (DDD) concept was introduced by first Eric Evans in 2003. The concept of microservices did not exist at that time. So basically DDD was introduced to solve the problem of a large monolithic code base. In the monolithic world, once the codebase starts growing with the growth of the business, it becomes difficult to maintain the code organized and structured as it was originally designed. Monolithic applications designed using MVC architecture have good separation between the business layer and the presentation layer. But in the absence of the strict architectural guidelines, the business layer does not provide specific rules to maintain responsibility boundaries between different modules and classes. That’s why as the code base grows it increases the risk of logic breakdown, responsibility leakage between the different components of the application.
評分和評論
4.2
15 則評論
關於作者
Nitesh Malviya is an IT Enthusiast having 13+ years of IT experience. Nitesh started his journey with a designer and grown step by step to developer and project manager later on. He learned about client interaction, client nurturing, and sales operations too. He is still learning and loves to engage him in new technologies. He also feel that now it's his moral duty to provide meaningful and easy content about the latest and trending technologies for newcomers. This will help him immensely in grooming his career in the right direction.
為這本電子書評分
請分享你的寶貴意見。
閱讀資訊
智能手機和平板電腦
手提電腦和電腦
你可以使用電腦的網絡瀏覽器聆聽在 Google Play 上購買的有聲書。
電子書閱讀器及其他裝置
如要在 Kobo 等電子墨水裝置上閱覽書籍，你需要下載檔案並傳輸到你的裝置。請按照說明中心的詳細指示，將檔案傳輸到支援的電子書閱讀器。
