![]() Over time, stack thinking emerged to help technologists accommodate the need for multiple software and hardware providers, and the need for certain components to be added-or removed-in the future. In the past, it was quite common for a stack to be one giant program where all functions were nearly inseparable. To dive deeper into a set of use cases for horizontal (or aggregation) strategies across stacks, you can read Scott Brinker's quick article " Matrixed Tech Stacks with Both Horizontal and Vertical Aggregation Platforms." Data processing and aggregation tools might best be used on 'data lakes' and 'data streams' that span multiple business units or geographies.Security and compliance tools ensure data security throughout an organization.Enterprise Resource Planning (ERP) software can coordinate a variety of functions and capabilities in large businesses, such as finance and HR.It is therefore relevant to marketing, finance, product development, legal, and several other functions, as well as to different product lines within the same company. ![]() Customer Relationship Management (CRM) software tracks contacts, transactions, and many other data points around clients and users.While stacks are often oriented around verticals (like finance or marketing within a company), some functions make more sense if they are 'horizontal.' Common horizontal functions include: Scope of your project: Is this a narrow, one-time project, or something which may grow and evolve over time? Stacks need to be able to grow as demands increase, but choosing The Most Capable Stack Ever Assembled may be overkill for a one-time problem or a product that will be discontinued soon.Ease of integration and interoperability: Does it connect fully with other stacks in your organization, or other partners and vendors with different stacks? Interoperability is vital in modern digital strategies.Variety of tools: Is there a variety of tools to choose from, or does one vendor require that only their tools be used, whether or not they are the best fit for the project?.Availability of talent: Are developers available who can work in your stack? A custom solution may seem cheaper-but it may be hard to train new developers.Security: Is the entire tech stack secure? Sometimes stacks based around fewer vendors are easier to secure.Scalability: Will the solution scale? What works for a small business or prototype project won't necessarily scale for an enterprise or a sudden boom in traffic.Time to market: How long until the product needs to be available? It may make sense to prioritize a proven but more expensive tech stack if time is tight.When selecting a tech stack (or its components), it's important to consider any tradeoffs or tensions among the following:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |