Solution Architecture - Enterprise Application Architecture
Rohan Rekhi
Servant Leadership | Data API Strategy | Data Engineering Delivery | Data Governance | Cloud Certified | Snowflake Architect | DataOps | Data Product | Asset Management | Technical Reviews | Biz Dev| Data Strategy
Thank you for reading my latest article here.
Here at LinkedIn, I regularly write about data architecture, Business Architectures Business Concepts and technology trends. To read my future articles simply join my Newsletter on LinkedIn or follow me on 'Rohan Rekhi | LinkedIn
In the last article I touched upon some aspects of Solution Architecture at High Level. Today Let's talk about Enterprise Application Architecture.
It has two important aspects
High Level Architecture and Application Development
It will have multiple aspects which needs to be considered:
In this article let's talk about Development Stack.
Purpose:
The Development Stack is a single page document that directs architects, developers and management to the approved options for software development and application composition. The items elaborated are in-line with the APM tool which is the authoritative resource. Where version is specified, it indicates the preferred supported version. This page is a quick reference for the technology stack that is elaborated in solution architecture documents and other technical artifacts. This page is living document and updated quarterly.??
Scope:
The scope of this page includes tools used during the Application Development lifecycle, from design through code. This can be a comprehensive list but not an exhaustive list. There are items not elaborated and this is by design.
Usage:
This is a quick reference for architecture/design and development team members and should be used along with additional specific guidance provided by other technical artifacts on Architectural Repository. For example, handbooks, patterns, and strategy artifacts. Specific usage within the context of a solution under construction must be reviewed by specific local and central governance bodies.
Here's the typical Technology stack landscape may look like
* Python is a specialty?language supporting business intelligence including development of ETLs and data pipelines.? Python also supports infrastructure scripting and IaC activities.? It is not for use in building applications, web APIs or UIs.?
** Cloud Composer only supports Python?
领英推荐
The mapping of languages to the use cases above should be strictly enforced.
It's ok to certain cells to be TBD as Solutions may be evaluated and as this is a living document. As and when decisions are updated appropriate names should reflect here.
This list can always have some footnotes. Some examples of footnotes as referenced in above table can be like this
In upcoming articles, I will zoom into multiple types of solutions mentioned above.
#applicationarchitecture #technologystack #frameworks #languages #distributed #cloud
To stay up to date with my latest articles in, make sure to subscribe to my newsletter follow me on LinkedIn , and if you or anyone in your network is interested in taking a deeper dive into some of these topics or looking for help with your initiatives and programs, please feel free to reach out to me. For wider reach please share.
You can also follow me on Medium and Subscribe to my articles there.
Microsoft Certified Azure Data Engineer |Certified TOGAF 9.2 |ICT Data and Information Architect - Azure |
2 个月Tshimangadzo Gloria Raphulu