What I learned as an Application Architect while creating my product

• dimanikulin

  3 1 9.9

  Config files for my GitHub profile.

  I began my journey as an architect with requirements selection. By selecting the right requirements, an architect can ensure that the software is designed to meet specific business goals and objectives, as well as technical and operational requirements. This helps ensure that the software is scalable, maintainable and meets the needs of both the end-users and the stakeholders. It's worth noting that my approach to selecting requirements differed from that of a product manager because I needed more technical requirements. I divided architect requirements into four parts:

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• fva

  6 10 9.4 C++

  A convergent tool set in form of desktop applications to automate the process of importing the multimedia data (photo/audio/video) into the IR multimedia systems like digiKam, Google Photo, Apple Photo, Synology Photo Station, etc. to make the multimedia more searchable and to improve family photos

  Initially, the list was much longer, but as some of the tools/libraries became outdated, I moved them to a separate table using the same format. You can find the old dependencies list here.

Suggest a related project