26 ms·
I think we mostly agree on this, but your phrasing, to me, makes it look as if you put all the intelligence at the architect side. I think that, ideally, the ar
by Someone 13y ago
I think we mostly agree on this, but your phrasing, to me, makes it look as if you put all the intelligence at the architect side. I think that, ideally, the architect should only specify what is needed, the admin should be in control of the how, and the two should discuss things on level footing.
And that what should be in purely abstract terms. Not "We need an Oracle database", not even "We need a SQL store*, but "We need a transactional store that can do x transactions per second, y a week, stores z TB of data, gets backed up daily, has 75% uptime and can be restored within a week" (note that that goes a lot further than your "only the set of APIs it expects". I guess/expect that you will agree that the non-functional stuff also must be included)