4 ms·
I think the need to maintain multiple team may not be as urgent if you constrain the timeline. The biggest requirement I see is automation. For this to be feas
by bob1029 6y ago
I think the need to maintain multiple team may not be as urgent if you constrain the timeline.
The biggest requirement I see is automation. For this to be feasible in a general sense, it has to be down to a single method invocation completes in 1 hour what those teams are doing in 2-3 years.
The biggest challenge that will emerge from trying to meet this objective is the import/export of data to/from these now-highly-ephemeral IT systems. The ability to easily import pure business data back into a fresh instance of the system will likely constrain the vendor & product choices as well.
Very soon, you might find yourself building a 100% custom vertical to support these objectives explicitly. I think this is ultimately inevitable and desirable though. We just need to learn how to build these things quickly & reliably.
- mlac 6y agoYeah I see it as two items - total architecture rebuilds and redesigns for an organization’s IT system vs. blowing away enterprise resources each night and restoring with a known good application each day or week. That would be amazing but incredibly complex. Each week I guess you would run a script to re-build your architecture in AWS with the latest builds and patches. Then run a config script to re-import all your data. It would be painful to figure out, but you could essentially store a copy of your data at another AWS location and fail over within a day or two just given your two install scripts (the architecture build out and then the config script to read in the data), Depending how often and on how many systems you did this on, you’d basically make attackers restart every night or week. And ideally you’re patching as quickly as possible, so it might block some of them out quickly.