3 ms·
the thing is, it doesn't really matter. someone has to figure out how to provision & configure a bunch of resources for the app, & too often that toolchain bloa
by rektide 6y ago
the thing is, it doesn't really matter. someone has to figure out how to provision & configure a bunch of resources for the app, & too often that toolchain bloats & becomes inaccessible to more & more of the company's developers, which wrecks the dev-ops feng-shui we all want. but it kind of doesn't matter. these are a kind of minor cost of doing software, truthfully.
the interesting bits in-development these days are not the toolkits to assemble cloud. the interesting bits are the cloud-ification of the application. rather than configuration & state being managed by the app, externalizing more & more of the inner-pieces of the app into external services really reduces the app foot-print, & gives all apps in the environment a common basis for operation. at the moment, it's pretty much only kubernetes doing anything here, & frankly, it's under-hyped, radically under-hyped, that this is the true-er goal of kubernetes. it's not just another platform. desired state management is a whole philosophy for computing, about writing what you want to do in to a central archive, then allowing autonomic systems to break down & accomplish the state you have told the system to set out for.
this hinges upon simple steps like externalizing your apps state into central/cloud systems along-side other app's state. it's practiced by writing separate controllers, a kind of inten-based CQRS 2.0. writing code to build state, as cdk does, is convenient & ops friendly. but still very procedural/computing 1.0. i very much look forward to a far better, far more expansive future, one that is far less isolated "me and my app" & much more bigger picture & all encompassing. kubernetes is bringing that. nothing else is, that i have seen.