"Exploring MACH Principles", Nikita Galkin
Denunciar
Compartir
•0 recomendaciones•52 vistas
"Exploring MACH Principles", Nikita Galkin
•0 recomendaciones•52 vistas
Denunciar
Compartir
Descargar para leer sin conexión
In his presentation, Nikita Galkin will unveil the core principles of MACH. While these principles may already be familiar to you individually, their collective implementation creates an impressive synergy. Join Nikita to understand what makes MACH an ideal choice for startups where "time-to-market" is crucial. We will begin with a microservice-oriented mindset, which works effectively even in monolithic systems. Next, we will uncover how the "API-first" approach accelerates integrations. We will reiterate the significance of the "Cloud Native" approach for ambitious startups and explore why it's essential. Additionally, we'll delve into how the "headless" architecture changes the perception of data interaction. Throughout the presentation, the focus will remain on these concepts and practical tools that aid in their realization. Join Nikita Galkin in this session to gain a new perspective on architecture and practical approaches to its implementation.
Recomendados
Más contenido relacionado
Similar a "Exploring MACH Principles", Nikita Galkin
Similar a "Exploring MACH Principles", Nikita Galkin(20)
Más de Fwdays
Más de Fwdays(20)
Último
Último(20)
"Exploring MACH Principles", Nikita Galkin
- 2. FRACTIONAL
- 3. Love and Know: ▰ How to make developers and business happy ▰ Technical and process debt elimination Believe that: ▰ Any problem must be solved at the right level ▰ Software is easy. People are hard ▰ A problem should be highlighted, an idea should be "sold", a solution should be demonstrated 3
- 4. Code Primary source code complemented by utilized libraries, SDKs and frameworks. 3 Infrastructure The foundational digital assets, including servers, databases, networking tools, and integrated cloud solutions, that support and enable system functionality. 4 Business Core functionality driven by business requirements. 1 API Interfaces for interaction RESTful APIs, GraphQL, WS, RPC, etc 2
- 5. MAIN IDEA: Your architecture requires clear principles
- 8. Microservices involve breaking down an application into a collection of loosely coupled, independently deployable services.
- 9. Business 01 Feature thinking ▰ Modular Design: Break down complex systems into individual features. ▰ Isolation: Each feature can evolve independently, ensuring agility. ▰ Prototyping and R&D: Rapid development and testing of features, leading to quicker innovation and adaptation.
- 10. If we had one week to implement this feature, what would it look like? Business 01 Feature thinking
- 11. API 02 Documentation ▰ API contracts languages: ▻ Swagger ▻ AsyncAPI ▻ GraphQL ▰ documentation ▰ breaking change ▰ versioning
- 13. Code 03 Code organization Microservices The application is fully decomposed into a suite of small services, each running in its own process and communicating with lightweight mechanisms Monolith The system is built as a monolith, but the code is organized in a modular fashion Hybrid Breaking out the most logical or manageable module/component from the monolithic system and turn it into a standalone microservice
- 15. Infrastructure 04 3rd parties services ▰ Externally Managed: Not under our direct control regarding uptime, changes, or updates. ▰ SLAs: They often come with defined performance, uptime, and support promises. ▰ Integration Points: Accessed via APIs, SDKs, webhooks or other integration mechanisms. ▰ Billing & Costs: Use often involves subscription fees or pay-as-you-go costs.
- 16. Infrastructure 04 3rd parties services ▰ Defined Function: Like a microservice, a 3rd party service typically provides a specific, well-defined function. ▰ Independent Deployment: These services are independently deployable and can be updated without affecting your system directly. ▰ Communicates Over Network: Both microservices and 3rd party services usually communicate over the network, often using HTTP/REST.
- 17. Infrastructure 04 3rd parties services Treating 3rd party services like microservices in your architecture can be beneficial for system design and understanding.
- 18. Infrastructure 04 3rd parties services
- 19. Code Primary source code complemented by utilized libraries, SDKs and frameworks. 3 Infrastructure The foundational digital assets, including servers, databases, networking tools, and integrated cloud solutions, that support and enable system functionality. 4 Business Core functionality driven by business requirements. 1 API Interfaces for interaction RESTful APIs, GraphQL, WS, RPC, etc 2
- 21. API-first refers to a development approach where the API (Application Programming Interface) is designed and developed as the first priority before any application UI or consumer application.
- 22. Business 01 Domain Language ▰ APIs expose the core business logic and functionality. ▰ Ensures consistent logic across all applications and platforms ▰ APIs can serve as a DSL (Domain Specific Language), ensuring terms and actions are business-centric.
- 23. API 02 Responsibilities ▰ Data access ▻ Pagination ▻ Filtering/Search ▰ Data modification ▻ Input validation ▰ Data aggregation ▰ ACL
- 25. Code 03 Low-code
- 27. CLOUD-NATIVE
- 28. This means that applications are designed to run on cloud infrastructure
- 29. Business 01 Time and money ▰ Using cloud services and 3rd parties to implement business features ▰ Focus on time to market with FinOps in mind later ▰ Hiring Cloud Engineers instead of DevOps&Backend Engineers
- 30. API 02 API for access to cloud services
- 31. Code 03 Logging and tracing ▰ Logs in Cloud format ▰ Logs routing ▰ Metrics collection ▰ Traces
- 33. HEADLESS
- 34. An architectural approach where the frontend (the "head") is decoupled from the backend, allowing each to operate independently.
- 36. Business 01 Content ▰ Business creates and owns content ▰ Content and digital assets plays important role in business ▰ Using headless to manage Digital Asset Management and Content
- 37. API 02 Headless CMS Headless APIs provide content as a service, meaning the content is accessible via API calls and can be delivered to any front end, be it web, mobile apps, kiosks, or other digital platforms.
- 38. Code 03 Static site generation
- 39. Infrastructure 04 Deployment on demand