I got AWS certified this week, and as I’ve been learning more about what goes into the design of various systems, it occurs to me that I don’t have an understanding of when a unique part of a system should be considered a pro or con.
For instance, it makes sense to me that we would want something like the database for an application to be deployed in multiple AZ’s to increase availability via no single point of failure.
It _also_ makes sense to me that if I’m using redux in a frontend web app, one benefit we get is the single source of truth around app state.
These two make sense to me independently, but I am struggling to understand how the evaluation around this differs depending on the context. My gut is telling me that I’m trying to compare two different levels of abstraction, but I just can’t quite come up with a rule for when one of these rules applies and the other one does not.
What questions should I be asking myself to determine which of these is appropriate to apply? Thanks
Comments URL: https://news.ycombinator.com/item?id=33307421
Points: 10
# Comments: 7
Continue reading...
For instance, it makes sense to me that we would want something like the database for an application to be deployed in multiple AZ’s to increase availability via no single point of failure.
It _also_ makes sense to me that if I’m using redux in a frontend web app, one benefit we get is the single source of truth around app state.
These two make sense to me independently, but I am struggling to understand how the evaluation around this differs depending on the context. My gut is telling me that I’m trying to compare two different levels of abstraction, but I just can’t quite come up with a rule for when one of these rules applies and the other one does not.
What questions should I be asking myself to determine which of these is appropriate to apply? Thanks
Comments URL: https://news.ycombinator.com/item?id=33307421
Points: 10
# Comments: 7
Continue reading...
