WEBVTT

00:00:00.280 --> 00:00:02.430
Your Torque app is one hotel.

00:00:02.840 --> 00:00:05.860
Each domain has its own keycard floor.

00:00:06.940 --> 00:00:11.540
Tasks needs boiler news, so Pockets borrows a master key.

00:00:12.330 --> 00:00:13.660
Assets renames a column.

00:00:14.210 --> 00:00:15.990
Tasks goes dark.

00:00:17.010 --> 00:00:20.160
Build with Torque keeps each domain on its own floor.

00:00:20.900 --> 00:00:24.650
To ask a neighbour, you call the coordinator on a line you declared.

00:00:26.480 --> 00:00:30.430
A boiler changes, and assets posts a past-tense fact.

00:00:30.960 --> 00:00:32.170
Tasks reacts.

00:00:33.150 --> 00:00:39.310
Out comes the plan: what tasks owns, what it needs, what works when a neighbour is gone.

00:00:41.220 --> 00:00:44.850
Data changes go to a mock-up floor first, with a way back.

00:00:47.090 --> 00:00:50.590
Its checks test the guide, not your running hotel.

00:01:03.600 --> 00:01:04.790
Build with Torque.

00:01:04.980 --> 00:01:07.560
Add a domain without tangling the application.