How fimyh/automatisation works
Project Type & Purpose
• Confirm from the README: Is it a web app, a microservice suite, a CLI tool, a library, a compiler, etc.?
• Primary goal: user-facing UI, data processing, API orchestration, language parsing, etc.
File Structure
• Top-level folders (e.g., frontend, backend, lib, services, scripts, tests).
• Spot patterns: MVC, microservices (multiple service folders), serverless functions, mono-repo vs. multi-repo.
• Config/build files (Dockerfile, docker-compose.yml, webpack.config.js, Makefile).
Extract Architecture Hints from README
• Described components (databases, caches, third-party APIs, message queues).
• Check for noted flows (e.g., “Client → API Gateway → Microservice A → Database”).
a. Frontend: frameworks (React, Angular, Vue), static assets, CDN, SSR vs. SPA layers.
b. Backend/API: Node.js/Express, Django/REST framework, Go microservices, GraphQL endpoints.
c. Data stores: relational (PostgreSQL, MySQL), NoSQL (MongoDB, Redis), search (Elasticsearch).
d. External Services: payment gateways, auth providers (OAuth, SAML), third-party APIs.
e. Infrastructure: load balancers, API gateways, message brokers (Kafka, RabbitMQ), CI/CD pipelines.
Architectural Patterns & Key Tech
• Tech stack next to each component: e.g., “Auth Service (Node.js + Passport.js)”.