> "architecture is hard, so let the smart people at Google handle it."
You are misunderstanding. I and others don't say its hard therefore we will get all our answers from one prophet.
We can look at lots of options (including rolling your own) then make a choice. Once I made a choice for a project its smart to comply with the architecture and principles provided by that choice.
I do the same thing on the web I do everywhere else. I dont write my own gui librarys or databases. I look at databases, evaluate them based on my needs and pick one or more. If I choice SQLDB I will not use it like a key value store, thus the database from now on forces me into a pattern, but that is alright because I have voluntarily made that choice.
If I have other needs I have to evaluate if I would rather bend SQLDB or add another database.
Knowing architecture is required for your choice but its a skill that you should not apply every day. Once you have to make your product happen in that architecture. It does no good to constantly rethink your hole stack.
You are misunderstanding. I and others don't say its hard therefore we will get all our answers from one prophet.
We can look at lots of options (including rolling your own) then make a choice. Once I made a choice for a project its smart to comply with the architecture and principles provided by that choice.
I do the same thing on the web I do everywhere else. I dont write my own gui librarys or databases. I look at databases, evaluate them based on my needs and pick one or more. If I choice SQLDB I will not use it like a key value store, thus the database from now on forces me into a pattern, but that is alright because I have voluntarily made that choice.
If I have other needs I have to evaluate if I would rather bend SQLDB or add another database.
Knowing architecture is required for your choice but its a skill that you should not apply every day. Once you have to make your product happen in that architecture. It does no good to constantly rethink your hole stack.