Bankmill’s Post

How do you get the current user in a Clean Architecture use case? Remember, you can't break the dependency rule to implement this. Use cases live in the Application layer, where you can't introduce external concerns. Let's say you want to know who the current user is to determine if they can access some resource. This is your typical resource-based authorization check. But you have to interact with the identity provider to get this information. This breaks the dependency rule in Clean Architecture. The solution? Start with an abstraction. The inner layers in Clean Architecture define abstractions for external concerns. From the Application layer's perspective, authentication and user identity are external concerns. Here's how you can easily implement this: https://lnkd.in/e24_XaSN --- ✍️ What would you add? ♻️ Reshare if you agree.

What are the benefits of event-driven architecture (EDA)? EDA provides a flexible, scalable, and real-time approach to processing actions and responses quickly. It is ideal for managing high volumes and high-velocity data in real-time with a minimum time lag. It can handle complex event processing, such as pattern matching or aggregation over time windows. https://buff.ly/43H5LrK

Easiest way to Scale your Applications: Queues and Background Workers Streamline your application's performance with queues and background workers. Queues ensure tasks are organized, preventing the main application from getting overwhelmed, while background workers handle them efficiently. This translates to faste user experience and a more scalable architecture.

The mediator design pattern is a behavioral pattern that defines an object, the mediator, to centralize communication between various components or objects in a system. This promotes loose coupling by preventing direct interactions between components instead of having them communicate through the mediator, facilitating better maintainability and flexibility in the system architecture. And we can use this pattern in various examples, e.g., testing and mocking, microservice architecture,... 🦦 https://lnkd.in/dmxMuWAN https://lnkd.in/d4eYJ4Rp #softwareengineering #designpattern #designs #mediatordesignpattern

MVP Architecture pattern : In MVP architechture we divide the project into three primary layer Presenter, View and Model View : This takes user control, handles the look and feel, positioning and alignment etc. It follows all the user interaction to the presenter. Presenter : Takes the input from the view, loads the model and updates the view accordingly. Model : This section has business logic.. In MVP the first hit comes to the view, view passes the call to presenter, Presenter calls the model and updates the view. Presenter updates the view via a call back.

Unlock the full potential of your applications with an Application Architecture Review! We ensure scalability, improve performance, and enhance security by identifying and addressing issues early. Invest in quality and efficiency for a robust, future-proof solution. #AppArchitecture #TechReview #PerformanceBoost

Unlock the full potential of your applications with an Application Architecture Review! We ensure scalability, improve performance, and enhance security by identifying and addressing issues early. Invest in quality and efficiency for a robust, future-proof solution. #AppArchitecture #TechReview #PerformanceBoost

The 4 Rules for Correct Application Composition The first two rules are the result of correctly using the Architecture Canvas methodology. The remaining two take into account other strategic considerations, driving the decision for creating smaller applications upfront. Rule #1 - Correctly layer your modules Follow the Architecture Canvas principles. If the module architecture contains violations, it may be impossible to get to a correct and manageable application architecture. Rule #2 - Correctly Layer Your Applications Apply the Architecture Canvas principles at the application level, not just the module level. #LogicaSys #Outsystems

Unlock the full potential of our applications with an Application Architecture Review! We ensure scalability, improve performance, and enhance security by identifying and addressing issues early. Invest in quality and efficiency for a robust, future-proof solution. #AppArchitecture #TechReview #PerformanceBoost"

Unlock the full potential of our applications with an Application Architecture Review! We ensure scalability, improve performance, and enhance security by identifying and addressing issues early. Invest in quality and efficiency for a robust, future-proof solution. #AppArchitecture #TechReview #PerformanceBoost