Chapter 2Looking at Fugue
In the first chapter we spun up our simple Fugue Ink application, verified its deployment in the AWS Console, and demonstrated Fugue’s enforcement of infrastructure. You defined the application’s infrastructure in a Ludwig composition file, FugueInk.lw, within which you imported a few basic libraries and declared the services responsible for the application’s execution and continuing operation. You used the CLI, the front end of the system that runs locally on your machine, to enter commands. Those commands told Fugue’s Conductor, the back end that runs remotely in AWS, what to do with the Ludwig file and its programming.
Mapping the characteristics of this system (or any system, for that matter) offers clarity to ...
Get Scalable Cloud Ops with Fugue 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.
