Tech Strategy
How do you understand and execute a Tech Strategy
Last updated
How do you understand and execute a Tech Strategy
Last updated
An overview of Architecture, Technologies and Technical practices. It should align with the company strategy and business cases. Like product strategy, it offers alignment, direction, guidance. It enables small and autonomous teams. It pushes decision making to the possible lowest level.
Strategies are also the bricks that narrow your many possible futures down enough that it’s possible to write a realistic vision. - Staff Engineer by Will Larson
If you realize that you’ve rehashed the same discussion three or four times, it’s time to write a strategy. When the future’s too hazy to identify investments worth making, it’s time to write another vision. If neither of those sound like familiar problems – move on to other work for now and return later
What technologies shall we use? AWS or GCP, Buildkite or TravisCI, NodeJs or .Net Core, GitHub or GitLab, React or Angular, Athena or BigQuery, Postgres or MySQL, OpenSearch or ElasticSearch, and more...and more...
You should probably follow the technologies that are commonly used in your organization.
What common architecture patterns should we use? N-Tire, CQRS, Event sourcing, or a combination of all of them. How do these services communicate with each other? REST or RPC. Is there a centralised authentication platform? Is there a Platform as a Service? Are there any shared utils that will improve developer productivity?
Data Platform as a Service: well-documented data ingestion, clear data ownership and governance, query schema, event catalogue, reporting and dashboarding.
