model for your existing integrations. For some new integrations, you might have some options.  Most of the changes that are required when moving towards more fine-grained and  decentralized integration align with cloud-native principles. The term  cloud-native  refers to a different approach to designing, building, deploying, and  administering components. If done well, it provides  implementation agility ,  infrastructure  optimization ,  discrete resilience , and  platform portability .  On a practical level, it encompasses the following items: 3.2.1 Moving to a cloud-native approach 3.2.2 Fine-grained deployment: Breaking up the ESB Figure 3-12 shows a fine-grained deployment.  Because of the potential benefits of breaking up applications into microservices, you should  consider breaking up the ESB into many separate modules so that each is on its own  separate run time with just a small collection of integrations inside.  We begin a description about breaking up the ESB into more, fine-grained  modular  components .  We touch on all of these items as we explore modernization of application integration. If you  are only vaguely familiar with cloud-native or any of these terms, see Chapter 4, “Cloud-native  concepts and technology” on page 85, which explains them in more detail.  GLYPH<SM590000> Modular components  GLYPH<SM590000> Stateless components  GLYPH<SM590000> Image-based deployment  GLYPH<SM590000> Elastic-neutral infrastructure  GLYPH<SM590000> Lightweight run times  GLYPH<SM590000> Log-based monitoring GLYPH<SM590000> API-based intra-app communication  GLYPH<SM590000> Event-driven architecture GLYPH<SM590000> CI/CD  GLYPH<SM590000> DevOps  GLYPH<SM590000> Agile methods  Chapter 3. Agile integration: Capability perspectives  55