Nour Matar

One of the benefits TDD brings to code is testability , and that solely means : - make everything function and give every function a meaningful name (Break your code into smaller, modular functions) - Maintain a Clear Flow of Control how to Maintain a Clear Flow of Control in code with callback functions ? the image below explains it #principle #clean_code #Jquery #javascript #tdd

2

#backend #test #structure #unit_test #integration_test 💡Are you ready to starting write automate test with Clean Architecture ? ✅at first you need solid structure for manage all tests :

14

Choosing Between Kafka and RabbitMQ for Your Spring Backend: Making the Right Messaging Choice . When it comes to building resilient and scalable Spring backend applications, choosing the right messaging system is crucial. Let's explore when to use Kafka or RabbitMQ to power your Spring backend: RabbitMQ: Lightweight and Flexible Messaging RabbitMQ is a robust and versatile message broker known for its simplicity and ease of use. It's an excellent choice for applications requiring traditional message queuing patterns, such as task distribution, pub/sub, and request/reply. With features like exchanges, queues, and bindings, RabbitMQ provides a flexible messaging infrastructure that can adapt to a wide range of use cases. Kafka: Scalable and High-Throughput Streaming Kafka is a distributed streaming platform designed for handling large volumes of data and supporting real-time stream processing. It excels in scenarios where high throughput, fault tolerance, and horizontal scalability are paramount, making it ideal for event-driven architectures, log aggregation, and real-time analytics. Kafka's durable and fault-tolerant design ensures data integrity and availability, even in the face of failures or network partitions. When to Use Kafka or RabbitMQ in Your Spring Backend: Use RabbitMQ when: •You need a lightweight and easy-to-configure messaging system. •Your application relies on traditional messaging patterns like queues and exchanges. •You prioritize simplicity and flexibility over high throughput and scalability. Use Kafka when: • You require high throughput, fault tolerance, and real-time stream processing capabilities. •Your application deals with large volumes of data and requires horizontal scalability. •You're building event-driven architectures or real-time analytics pipelines. Choosing the Right Tool for the Job Ultimately, the decision between Kafka and RabbitMQ depends on the specific requirements of your Spring backend application. By understanding the strengths and trade-offs of each messaging system, you can make an informed choice that aligns with your application's needs and goals. #Spring #Backend #Messaging #Kafka #RabbitMQ #SoftwareArchitecture #RealTimeProcessing #EventDriven

20

I found this article interesting to read ! Maybe we should think twice before overusing usecases #clean_architecture #usecases #software_design

2

#MediatR #Github #Repo #Repository 💡Would your like check MediatR configuration? Such as command /commandHandler or Notifications. ✅With this Repository you can check all connections in MediatR.

24

Hello .NET Developers, Today, we are going to discuss the first primary challenge: 𝐃𝐞𝐟𝐢𝐧𝐢𝐧𝐠 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞 𝐁𝐨𝐮𝐧𝐝𝐚𝐫𝐢𝐞𝐬 𝐏𝐚𝐫𝐭 𝟏. Some important points to consider are: 1-𝐌𝐞𝐚𝐧𝐢𝐧𝐠𝐟𝐮𝐥 𝐒𝐞𝐩𝐚𝐫𝐚𝐭𝐢𝐨𝐧 𝐎𝐯𝐞𝐫 𝐆𝐫𝐚𝐧𝐮𝐥𝐚𝐫𝐢𝐭𝐲: The primary goal is not to achieve the smallest possible microservices but to ensure meaningful separations based on business capabilities and domain knowledge. 2-𝐂𝐨𝐡𝐞𝐬𝐢𝐨𝐧 𝐚𝐧𝐝 𝐃𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐢𝐞𝐬: High cohesion within a service and minimal dependencies across services indicate well-defined boundaries. Services with a high number of interdependencies should be considered for merging. 3-𝐈𝐭𝐞𝐫𝐚𝐭𝐢𝐯𝐞 𝐏𝐫𝐨𝐜𝐞𝐬𝐬: Determining the right size and boundaries for microservices is an iterative process. As you gain more domain knowledge, you should adapt the boundaries and sizes accordingly. 𝐻𝑎𝑣𝑒 𝑦𝑜𝑢 𝑓𝑎𝑐𝑒𝑑 𝑎𝑛𝑦 𝑐ℎ𝑎𝑙𝑙𝑒𝑛𝑔𝑒𝑠 𝑤𝑖𝑡ℎ 𝑡ℎ𝑖𝑠 𝑖𝑛 𝑦𝑜𝑢𝑟 𝑝𝑟𝑜𝑗𝑒𝑐𝑡𝑠? 𝑆ℎ𝑎𝑟𝑒 𝑦𝑜𝑢𝑟 𝑒𝑥𝑝𝑒𝑟𝑖𝑒𝑛𝑐𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑐𝑜𝑚𝑚𝑒𝑛𝑡𝑠 𝑏𝑒𝑙𝑜𝑤! #mgendi #DOTNET #Microservices #Azure

24

1 commentaire

How to engineering distinguished software by 7 golden rules: 1-Apply best practices to ensure about deliveries' quality 2-Follow the Git Flow 3-Have strong principles of code review 4-Write tests as much as business gives you time 5-Be receptive to technical discussions 6-Automate as much as you can, ex: CI/CD 7-Write strong linter rules #software_engineer #flutter #mobile #kotlin #dart #java

6

New Project Begins 🔥 Backend : .Net Core Web API Frontend : Vue 3 #netcore #asp #vue #javascript #onionarchitecture #ef #efcore #microsoft #backend #frontend

17

Dependency Inversion + DDD = Domain-centric architecture A few famous examples are: - Hexagonal (ports & adapters) - Onion architecture - Clean architecture Clean architecture places the business logic and domain model at the application center. Use cases are also part of the core of the application. They orchestrate the domain model and tell it what to do. It's interesting how the dependencies between layers work. The inner layers define abstractions (interfaces). The outer layers implement these interfaces. At run time, the concrete implementations replace the interfaces. This allows you to hide the internals of things like SMS messaging, email, caching, etc. Another benefit is improved testability. The application core doesn't depend on infrastructure. So, it's easy to write automated unit tests for this layer. However, I find myself moving towards a more feature-driven approach. Similar to what Vertical Slice Architecture proposes. I will also break the dependency rule and introduce EF/Dapper in the Application layer. The thing is, I know how to maintain this kind of system. I know when to introduce an abstraction or refactor the use case. You can only learn this from experience and building many systems (and making a few mistakes). So don't obsess over architecture too much. Having the freedom to make the right architectural choice is what matters. When would you pick the Clean Architecture? Source: Milan Jovanović

12

1 commentaire

RabbitMQ vs Kafka vs ActiveMQ Let's dive into the key differences between RabbitMQ, Kafka, and ActiveMQ to help you make an informed decision. 1. RabbitMQ: A powerful message broker known for its robust routing capabilities. It uses an exchange to distribute messages to various queues, making it ideal for complex routing scenarios. Perfect for scenarios requiring advanced message patterns and flexible routing. 2. Kafka: Designed for high-throughput and fault-tolerant messaging, Kafka excels in real-time data processing. With its topic-based architecture, it allows for efficient data streaming and processing, making it a go-to choice for big data applications and event-driven architectures. 3. ActiveMQ: Known for its versatile protocol support, ActiveMQ is a reliable choice for applications requiring a range of communication protocols. Its protocol manager facilitates seamless integration with different systems, ensuring smooth message delivery and processing. Choosing the right tool depends on your specific needs and use cases. Whether it's RabbitMQ's flexible routing, Kafka's high-throughput capabilities, or ActiveMQ's protocol versatility, each has its unique strengths to offer. Credit by : Piyush Ranjan

1

Hello my friends , today i want to share with you important differences between [ #Global_Values ] properties in #CSS where most people that have conflict with it so needed to solve that thought provide the main difference between initial and inherit and unset and revert and all properties so let's get started : 1- inherit : That used the same value of parent of element 2- initial : value in CSS sets a property to its default value, which is the value the property would have if no value had been specified. 3- unset : - if this property can be inherit do that [ new changes ] - if we have state rejected inheritance operation will do initial like border with button and another example 4- revert : same initial idea but as normal values to properties based on user agent [ browsers settings ] 5- all : unset; wherever with any another attribute so be as : Implementation normal concept to each property not for specific property! Thank you for see it and see you in next post , good luck :)

2

Migrate from MVVM to MVI New Repo with MVI Architecture : Code Architecture (MVI) Jetpack Compose Clean Architecture Modularization Flow & StateFlow to give view the data and notify it when a change occurs. Dagger-hilt to handle dependency injection. Co-routines to deal with threads. Retrofit2 & OkHttp3 to handle apis requests. Room DataBase to cache the data and display it in case there is no internet Coil to load images from internet. check it now #compose #android #mvvm #mvi

89

3 commentaires

This Saturday @ 19:00 we will explore the latest updates and trends in the PHP ecosystem, come and say hi to Imad and me 👋 https://lnkd.in/enwrd3ij #php #community #laravel #symfony

76

1 commentaire

My New Weather App Developed With Rest Api.Empower Your Day with WeatherWise: Your Ultimate Weather Companion 🌦️ Repository:https://lnkd.in/dTi6k8xz #weather #rest_api #database #weather_app

14

Clean architecture

1

What’s new in Flutter 3.22 ? ... ... ... WebAssembly With the release of Flutter 3.22, Wasm is now available on the stable channel, offering significant performance improvements. In our internal benchmarks using Chrome on an M1 MacBook, the Wonderous app’s frame rendering time improved by 2x on average and 3x in worst-case scenarios. Engine Flutter 3.22 introduces significant updates to Impeller, the rendering engine that powers your Flutter applications. Key highlights include the completion of the Vulkan backend on Android for smoother graphics and improved performance, ongoing optimizations for blur effects and complex path rendering, and a new experimental API for testing with Impeller. Blur performance improvements Stencil-then-Cover Predictive back gesture Platform views improvements End of support for KitKat

7

1 commentaire