![]() ![]() Someone who can do the db optimization of yesteryear's DBA, that is also well-versed in different data types across all code bases and platforms used. ![]() Major initiatives/code additions can get stopped in their tracks and have to get unstuck by a data architect. Making fundamental changes to core database tables have far-reaching consequences, and require the input of the longest-tenured employees who have siloed knowledge about what is affected. Imagine a company that's had a robust ETL pipeline and a good set up for several years, but code has gotten fragmented across many teams. Architect would make the final decision on those replacements. They need to go out and make major replacements in their stack. Imagine a company with lots of data currently using a certain stack, but there have been bottlenecks and other issues investigated that don't have a good solution. Some abstract examples that might give you a better idea: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |