Learning Journey #1: Unraveling the Microservices Architecture

Welcome to the "Learning Journey" series. This space is my personal archive where I share insights and discoveries from my explorations into new tech territories, particularly back-end development and cloud services. As I continue to broaden my tech understanding, I hope this series inspires and contributes to your own learning journey.

Understanding Monolithic Architecture

Before we dive into MSA, let's first talk about Monolithic Architecture. In this architectural style, all software components of an application are interconnected and interdependent. This architecture is simple to develop, test, and deploy initially. However, as the application grows, the complexity increases, making it challenging to maintain and scale.

One of the significant drawbacks of a Monolithic Architecture is the need to build and deploy the entire system, even for a minor function change. This can lead to longer development cycles and makes continuous deployment challenging.

The Emergence of MSA

Due to these characteristics, monolithic architecture isn't suitable for certain types of systems. Microservices Architecture (MSA) can address these limitations by offering increased flexibility, scalability, and deployment speed by dividing the application into smaller, independent services.

Defining MSA

Microservices Architecture (MSA) structures an application as a set of small, independent services, each corresponding to a specific business functionality. Here are some key points:

Decomposition: Applications are broken down into smaller components or services. Each service can be developed, deployed, and scaled independently.

Independence: Each microservice functions independently, allowing changes to be made to one without affecting others. This promotes flexibility and accelerates development and deployment cycles.

Scalability: MSA's significant advantage is its scalability. Individual services can be scaled based on their requirements, leading to more efficient resource use.

Strengths and Weaknesses of MSA

While MSA provides numerous advantages, it's not without its drawbacks. Let's delve into both:

Strengths

  1. Scalability: Each service can be individually scaled based on its requirements.
  2. Independence: Changes can be made to one service without affecting others.
  3. Speed of Deployment: With smaller, independent services, changes can be deployed faster.

Weaknesses

  1. Increased Complexity: MSA might lead to unnecessary fragmentation of services, making management difficult.
  2. Problem Isolation: Identifying the service responsible for a problem can be challenging.
  3. Communication Failures: The need for services to communicate can introduce potential points of failure.
  4. Human Resources: Each service requires its own management, which could demand more human resources.
  5. Potential Performance Issues: The inter-service communication could potentially cause a slowdown in the system's speed.

When considering adopting MSA, it's essential to weigh these strengths and weaknesses against the specific needs and capabilities of your organization."

When to Use MSA

MSA isn't a one-size-fits-all solution. It's suitable for large, complex applications that require high scalability and flexibility. For small, simple applications, a monolithic architecture may be more appropriate.

Comments

Post a Comment

Popular posts from this blog

Daily#6. Understanding and Using NetworkCallback in Android

The NetworkCallback class plays a crucial role in handling network changes in Android. It allows apps to monitor the network's state and perform actions accordingly. It has different types such as DefaultNetworkCallback, Request type NetworkCallback and Listen type NetworkCallback. Default Network  In Android, the "default network" refers to the network that is currently being used for internet traffic. Most of the time, it is the network that your device is connected to for accessing the internet, either via Wi-Fi or mobile data.  The default network can change based on factors like network availability, signal strength, and user preferences. For instance, if you're connected to both Wi-Fi and mobile data, Android generally defaults to using Wi-Fi because it's typically faster and doesn't incur data charges. However, if the Wi-Fi signal becomes weak or disconnects, Android will automatically switch the default network to mobile data (if available) to maintain
Read more

Daily#11. Establishing Wi-Fi Connection using WifiNetworkSpecifier and WifiNetworkSuggestion

 Welcome back to our daily tech series! Today, we're diving into how to connect to a Wi-Fi network programmatically in Android using WifiNetworkSpecifier and WifiNetworkSuggestion APIs. WifiNetworkSpecifier WifiNetworkSpecifier is a part of the Android 10 (API level 29) addition to the Wi-Fi API. It allows applications to force Wi-Fi connections with specific networks programmatically. However, please note that the system will limit the number of outstanding requests to 100 per app. If this limit is exceeded, an exception will be thrown. Here's a simple example of how to use it: WifiNetworkSpecifier specifier = new WifiNetworkSpecifier.Builder() .setSsidPattern(new PatternMatcher("test", PatternMatcher.PATTERN_PREFIX)) .setWpa2Passphrase("test1234") .build(); NetworkRequest request = new NetworkRequest.Builder() .addTransportType(NetworkCapabilities.TRANSPORT_WIFI) .setNetworkSpecifier(specifier) .build(); ConnectivityManager connecti
Read more

Daily#14. Understanding JVM, Dalvik, and ART: The Engines Behind Java and Android Applications

Image
Introduction Developing applications in Java or for the Android platform requires an understanding of the runtime environments where these applications run. A runtime environment refers to the state of the system when a program is executed. It includes the settings, libraries, and other supporting infrastructure that the system provides to the program. Understanding runtime environments is crucial as they dictate how a program will behave when executed. Java Virtual Machine (JVM) is the original runtime environment for Java, but is not used on Android. Dalvik and ART, on the other hand, are newer runtime environments that were specifically designed for Android. This post will guide you through the functionality of JVM, Dalvik, and ART. What is JVM? The Java Virtual Machine (JVM) is an abstract computing machine that enables a computer to run a Java program. Here are the key characteristics of JVM: https://en.wikipe
Read more