Cloud dependency injection pattern
One benefit to the previous bootstrap pattern was that we were able to separate small configurations of the instance at start-up. This allowed us to alleviate some maintenance headaches, such as modifying the web page content on-the-fly. Imagine that the application consists of multiple web servers or even servers with entirely different purposes. For example, the user data we provided for the web server is not relevant to a database instance.
To take this further, we could separate it even further and have a common set of user data across all instances. This user data could go to S3 and get the actual configuration script it needs, whether that is to set it up as a web server or a database server, and run that. ...
Get Implementing Cloud Design Patterns for AWS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
