ApplicationChannel. Once these methods are finished executing, the application starts sending HTTP requests through the channel created by the
ApplicationChannelis a type - and can be instantiated - Conduit simply creates a number of isolates and instantiates
ApplicationChannelfor each. The initialization code is therefore identical for each isolate, which means that the ongoing behavior of each isolate is also identical.
entryPointin an application channel will be invoked on each isolate. This behavior is guaranteed to occur for each isolate and there is often little to worry about.
ApplicationChannel.initializeApplication, code runs on the main isolate. Any changes to static variables or singletons will not be replicated to the isolates running the application logic. The use case for this method is rather minimal, but it is very important that types like
CodecRegistryaren't configured in this method.
conduit serve. While less than 3 isolates will most certainly degrade performance, more than 3 doesn't necessarily improve performance. (And many more will certainly degrade performance.)
wrkand Observatory to profile your application and tune accordingly. In a multi-instance environment, remember that the total number of database connections is MxN, where M is the number of machines and N is the number of isolates.