What should be considered when deciding whether to split our monolithic web application into separate web applications using DDD?

Question

Background

We use the Microsoft Technology Stack (.NET).

We currently have a large monolithic web application. We are planning how to implement a domain-driven project.
We plan to implement microservices in some limited contexts, but not for everyone. Since this is a monolith, most limited contexts will live in the same database, so we will need to make sure that we control access at the code level.

From this SO post, there are two ways to implement restricted contexts.

<bc 1>
 |_ domain
 |_ application
 |_ presentation
 |_ infrastructure
<bc 2>
 |_ domain
 |_ application
 |_ presentation
 |_ infrastructure

or the following:

domain
 |_ <bc 1>
 |_ <bc 2>
application
presentation
infrastructure

. , .

: , , - . ?

( ) :

Products
Client Administration
System Administration

, .

. .

Answer 1

, 1.

" " , REST API. , , Product, Client System , -.

: http://blog.xebia.com/the-monolithic-frontend-in-the-microservices-architecture/ http://samnewman.io/patterns/architectural/bff/#bff