Skip to main content

Microservices

Microservices is a service-oriented architecture pattern wherein applications are built as a collection of various smallest independent service units.

They get their name because each function of the application operates as an independent service.

This architecture allows for each service to scale or update without disrupting other services in the application.

Example for e-Commerce Microservice:

In Below architecture diagram explained implementing simple Microservice module.

   Advantages of Microservices:

  • Microservices are self-contained, independent deployment module and independently manageable services.
  • Change or upgrade each service individually rather than upgrading in the entire application.
  • Enable easy integration
  • Less dependency and easy to test.
  • Dynamic scaling.
  • Faster release cycle.
Advantages of Microservices:

  • Microservices has all the associated complexities of the distributed system.
  • There is a higher chance of failure during communication between different services.
  • Difficult to manage a large number of services.
  • The developer needs to solve the problem, such as network latency and load balancing.
  • Complex testing over a distributed environment.

How Cloud (AWS) helps deploying and running Microservice based applications?

Computing power: AWS EC2 Elastic Container Service and AWS Lambda Serverless Computing

Storage: Secure Storage (Amazon S3) and Amazon ElastiCache

Databases: Amazon RDB, Amazon Aurora, Amazon DynamoDB

Networking: Amazon Service Discovery and AWS App Mesh, AWS Elastic Load Balancing, Amazon API Gateway and AWS Route 53 for DNS

Messaging: Amazon SQS for message queuing and SNS for publishing and notifications

Monitoring: AWS Cloudtrail for API monitoring and Amazon CloudWatch for infrastructure monitoring

DevOps and CI/CD: Amazon Container Image Repository (Amazon ECR) and other DevOps tools for enabling CI/CD workflows.


Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more