Показать сообщение отдельно
Старый 29.05.2017, 18:41   #7  
belugin is offline
belugin
Участник
Аватар для belugin
Сотрудники Microsoft Dynamics
Лучший по профессии 2017
Лучший по профессии 2015
Лучший по профессии 2014
Лучший по профессии 2011
Лучший по профессии 2009
 
4,622 / 2922 (107) +++++++++
Регистрация: 16.01.2004
Записей в блоге: 5
https://www.infoq.com/articles/monolith-defense-part-1


Key Takeaways
  • Both monoliths and microservices are viable architectures, though a monolith must be modular to be sustainable. Monoliths probably fit better for complex domains (enterprise apps), while microservices are more suited to internet-scale applications with simpler business domains.
  • Going with a microservices architecture means foregoing both transactions and referential integrity across modules/services. This necessarily comes with an implementation cost.
  • Either architecture requires a platform to support it. For microservices, much of the support relates to the complications that a network introduces (for example circuit breakers). For monoliths, the platform needs to handle cross-cutting technical concerns to allow the developer to focus on the complexity of the domain.
  • Going “Monolith First” (building the application as a modular monolith initially with the aim of breaking it into microservices later) requires that the modules’ boundaries, interfaces and responsibilities are well-defined.
За это сообщение автора поблагодарили: ax_mct (5).