3 ms·
In the days of cloud-hosted, microservice-based web applications, "architecture" in the infrastructural sense becomes less relevant. It's just a cloud server se
by bluetomcat 4y ago
In the days of cloud-hosted, microservice-based web applications, "architecture" in the infrastructural sense becomes less relevant. It's just a cloud server serving HTTP requests, having seamless access to vendor-provided elastic data stores, message queues, etc.
What remains relevant, though, is the "software architecture" – how you structure your data, what kinds of abstractions do you build over that data, is the data model suitable for the task at hand, etc.
- rswail 4y agoPart of the problem there is "in the infrastructural sense". Architecture is not about infrastructure at all. Infrastructure provides the constraints that the design must accomodate within its functional and non-functional requirements. It's how you use that infrastructure. Is it event-sourced, CQRS, eventually consistent? How are your services structured? Around resources with state transfer and media types, or more RPC? That's the architectural choices.
- zcmack 4y agoin my experience, having access to the aws dashboard rarely indicates mastery of the platform and knowledge of which tool is best for the job. it is incredibly common to lift and shift on premise workloads to ec2 with an rds instance to save the cognitive load of application refactoring. this creates a different flavor of infrastructure complexity without taking full advantage of the services on offer.