Cached config with expressive swoole

#1

I’m maintaining an expressive application for which I’m providing a docker container. This app is using swoole.

I’m trying to make this app as stateless as possible, and I was thinking if, taking into account how swoole shares loaded files between requests, does it really add any value to cache the merged configuration into a single file with zend-config-aggregator?

Currently I’m deleting the cached file as part the container entry point, otherwise, if a new config is provided using an env var, you have to delete the container entirely, or it is ignored.

Am I correct assuming I can drop this config cache and it won’t have a performance impact when serving the app with swoole?

#2

That should be the case

2 Likes
#3

Ok, thank you :slight_smile: