7.3 When does IBM App Connect need a local MQ server? 7.3.1 Benefits of being dependency-free in container-based environments 452  Accelerating Modernization with Agile Integration We have discussed a variety of common criteria based on functional (domains) versus  non-functional (scaling, availability), volatility versus stability, and various forms of  dependencies (such as MQ, data models). What’s clear is that some of these criteria are overlapping so we have discussed the  importance of establishing priorities, beginning with high-level business ownership and  working down to more pragmatic concerns. We have provided a simple framework for making your own decisions about grouping of  integrations as you move on your containerization journey. However, we recognize that every  enterprise is functionally different, with a differently evolved landscape, and different business  priorities.  We should of course always aim to design our integrations such that they are strongly  independent of one another. This way we can easily change our mind about the grouping  decisions and implement that change with minimal risk.  Note:  The following section was correct at the time of writing the book. However, changes  are anticipated in the relatively near term that will further reduce the need for a local MQ  server for IBM App Connect. For the latest information on this, check the blog post from  which this section was created, which will be updated to reflect any changes when they  occur.  https://developer.ibm.com/integration/blog/2018/06/21/ace-need-local-mq-server/ Back in 2015, with v10 of IBM App Connect (at that time known as IBM Integration Bus), the  hard dependency on a locally installed IBM MQ server was removed. Since that time, we  have been able to install IBM App Connect completely independent of MQ making the  installation and the resultant topology lighter and simpler. With the move toward more  granular installation of integrations, especially in containers, knowing exactly when we can  exploit this more lightweight installation has become all the more relevant. In this section, we explore when we can install IBM App Connect independently and,  conversely, under what circumstances might we still need a locally installed IBM MQ server?  Put another way, when do we really need a local IBM MQ server as opposed to when will it be  sufficient to connect to remote MQ servers? There are two very different reasons IBM App Connect makes use of IBM MQ: As explained later in this article, it is only the latter use of MQ that is the real driver for a  locally installed MQ server, but read on as this use might be less common than you thought. The question of whether IBM App Connect requires a local MQ server becomes more  pertinent as we move to container-based deployment and we explore installation of  integrations in a more granular way. Rather than having a single installation that contains  GLYPH<SM590000> As an asynchronous messaging provider GLYPH<SM590000> As a co-coordinator for global (two-phase commit) transactions