title: Microservices vs multi-layered architecture
body: <p>My project has one backend service (Web API) and one frontend SPA application. Backend service has presentation, application services, domain and infrastructure layers located in different .net assemblies. Domain layer has business domain objects, infrastructure – communication with external data and other stuff, application services – set of services used by presentation layer, presentation – Web API controllers. I think it’s very common layered architecture.</p>
  
  <p>Our new architect announced we are going to move backend to microservices architecture braking down our layers and dividing domain, application service and infrastructure layers to a few services and convert presentation layer to backend for frontend layer (as <a href="http://samnewman.io/patterns/architectural/bff/" rel="noreferrer">here</a> described). In feature, we are going to have mobile application. Sql Server database is going to leave as is for now.</p>
  
  <p>I don’t have experience with microservice architecture, so my questions are: 
  Is multi-layered architecture out of fashion already? What benefits and problems can bring such architecture design for my application?</p>