Micro services : Simplified architecture

-
Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are. Highly maintainable and testable. Loosely coupled. Independently deployable. Organized around business capabilities.












Here are the steps to designing a microservices architecture:
1. Understand the monolith
Study the operation of the monolith and determine the component functions and services it performs. 

2. Develop the microservices
Develop each function of the application as an autonomous, independently-running microservice. These usually run in a container on a cloud server. Each microservice answers to a single function – like search, shipping, payment, accounting, payroll, etc.

3.  Integrate the larger application
Loosely integrate the microservices via API gateways so they work in concert to form the larger application. An iPaaS like Factory can play an essential role in this step.

4. Allocate system resources
Use container orchestration tools like Kubernetes to manage the allocation of system resources for each microservice.


Benefits 

Simpler To Deploy

Deploy in literal pieces without affecting other services.

Simpler To Understand

Follow code easier since the function is isolated and less dependent.

Reusability Across Business

Share small services like payment or login systems across the business.

Faster Defect Isolation

When a test fails or service goes down, isolate it quickly with microservices.

Minimized Risk Of Change

Avoid locking in technologies or languages - change on the fly without risk.

Docker containerized applications for micro services 

(AZURE)



Comments

Post a Comment

Popular posts from this blog

Spark Cluster

-
Image
Spark applications run as independent sets of processes on a cluster, coordinated by the   SparkContext   object in your main program (called the   driver program ). Specifically, to run on a cluster, the SparkContext can connect to several types of  cluster managers  (either Spark’s own standalone cluster manager, Mesos or YARN), which allocate resources across applications. Once connected, Spark acquires  executors  on nodes in the cluster, which are processes that run computations and store data for your application. Next, it sends your application code (defined by JAR or Python files passed to SparkContext) to the executors. Finally, SparkContext sends  tasks  to the executors to run. There are several useful things to note about this architecture: Each application gets its own executor processes, which stay up for the duration of the whole application and run tasks in multiple threads. This has the benefit of isolating applications from ...
Read more

DORA Metrics

-
 DORA metrics, often referred to as the DORA (DevOps Research and Assessment) metrics, are a set of key performance indicators (KPIs) used to measure and assess the effectiveness of an organization's DevOps practices. DORA metrics were developed by the DevOps Research and Assessment team, which includes notable figures in the DevOps community such as Dr. Nicole Forsgren and Jez Humble. The DORA metrics encompass four key areas: 1. **Deployment Frequency:** This metric measures how often an organization deploys code changes to production. Higher deployment frequencies indicate a more agile and responsive development process. 2. **Lead Time for Changes:** This metric tracks the time it takes for code changes to go from code commit to being deployed in production. Shorter lead times suggest efficient and streamlined development and delivery processes. 3. **Mean Time to Recover (MTTR):** MTTR measures how quickly an organization can recover from failures or incidents in production. Low...
Read more