• Home
  • Archive
  • Tools
  • Contact Us

The Customize Windows

Technology Journal

  • Cloud Computing
  • Computer
  • Digital Photography
  • Windows 7
  • Archive
  • Cloud Computing
  • Virtualization
  • Computer and Internet
  • Digital Photography
  • Android
  • Sysadmin
  • Electronics
  • Big Data
  • Virtualization
  • Downloads
  • Web Development
  • Apple
  • Android
Advertisement
You are here: Home » The Fundamentals of Microservices

By Abhishek Ghosh February 13, 2021 5:06 pm Updated on February 13, 2021

The Fundamentals of Microservices

Advertisement

Microservices is composed of independent processes which communicate with each other via language-independent programming interfaces. The services are largely decoupled and do a small job. In this way, they enable a modular design of application software. The idea behind microservices is largely in line with the Unix philosophy – Do One Thing and Do It Well. The services should usually have the following characteristics:

  • The services can be easily replaced.
    The scope of a microservice should be manageable for each team member.
    A microservice should be able to be recreated and replaced by the appropriate team (usually 5 to 7 developers) with reasonable time (within one month).
  • A microservice should implement a bounded context in the sense of domain-driven design.
    The services have a single business function. For example, you can include an order process, registration, or invoicing, but not several of these things.
  • The user’s benefit is the focus.
    The core functionality should be delivered early to provide the earliest possible benefit.
    Interfaces should be self-documenting via Humane Registries. For example, Swagger for JSON-based REST services.
    After a new version of the service is deployed, the old version of the endpoint must be deployed for some time.
  • A microservice is developed by only one team. Conway’s law ensures that the architecture is also protected by organizational measures. Similarly, a team can be responsible for several professionally related microservices.
    Communication overhead and conflicts of interest between teams are avoided.
  • The interfaces hide implementation details.
    It should not be clear which architecture was used to implement a service. Standard low overhead methods, such as REST, are preferably used.
    Databases are not used by multiple services, but only by a single service. This also applies to views and stored procedures. Otherwise, the architecture is published through the database and transaction security, data integrity, and versioning cannot be ensured.
  • Microservices are isolated from other services.
    Each microservice can use a different programming language, database, or a completely different technology stack.
    Each microservice can be put into production independently of other microservices. This facilitates a high degree of automation and enables continuous delivery.
    Objects that occur in multiple bounded contexts are implemented separately in each service. For example, in an authentication system, an ordering system, a logistics system, and an invoice system, the same customer is represented by different objects because the objects are subject to different requirements.
    Microservices are delivered in separate OS containers, virtual machines, or servers. This ensures the service against another service overloading the host system.
  • Like all services, microservices must be secure:
    Microservices should be decentralized and scaled horizontally. Functional architectures with state-of-the-city architectures are preferred. This includes caches (for storing user sessions) that must be run as a separate service, such as an in-memory key-value database.
    Microservices isolate error events and states from other services.
    Logging, monitoring and operations databases enable observability.
    Authentication, authorization, and cryptography protect the data from unwanted access.

The size of a microservice is limited by the fact that network communication between microservices can be resource-intensive and a separate deployment must be provided for each microservice.

The Fundamentals of Microservices

 

Typical Components of a Microservice Architecture

 

Microservices require a lot of infrastructures, which is implemented by standalone services. Load balancers are used for load distribution of external HTTP requests from clients. Static content is delivered via a content delivery network.

Advertisement

---

The services responsible for business requirements are supported by a range of platform or infrastructure services. These perform key tasks such as application and service monitoring, logging web services, operations databases, configuration management, encryption, authorization and authentication, as well as autoscaling, software distribution, A/B testing and fault injection testing (FIT). There are also central routing services that are used to map URLs to instances with the respective services. Also, there are services for data persistence, especially caching, relational databases and NoSQL databases, as well as BLOB storage for any files.

Both SOA (Service-Oriented Architecture) and Microservices use services as architectural elements. SOA uses services to integrate different applications. The combination of services is done by orchestration or choreography, and portals can provide a common user interface (UI) for all services. Microservices structure an application through services. Each microservice can contain a user interface and implement business processes found in the orchestration in SOA.

Also read Advantages and Disadvantages of MicroServices.

This Article Has Been Shared 360 Times!

Facebook Twitter Pinterest
Abhishek Ghosh

About Abhishek Ghosh

Abhishek Ghosh is a Businessman, Surgeon, Author and Blogger. You can keep touch with him on Twitter - @AbhishekCTRL.

Here’s what we’ve got for you which might like :

Articles Related to The Fundamentals of Microservices

  • What Is a Serverless Microservice?

    What Is a Serverless Microservice? Serverless microservices run within vendor’s serverless infrastructure only when they are needed by the application.

  • What is the Relationship Between Serverless Computing and Microservices?

    What is the Relationship Between Serverless Computing and Microservices? They refer are two different ideas of architecture yet can be used together.

  • Does Serverless Computing Offer the Benefits of Microservices?

    Does Serverless Computing Offer the Benefits of Microservices? Both of them can be combined.There are more overheads for both Serverless and Microservices.

  • The Need for Monitoring the Microservices Environment

    To quickly identify and fix problems and errors, it is necessary to closely monitor the microservice architecture with some principles.

  • How To Install Apache Beam

    Apache Beam is a programming model to define and execute data processing. Here is How To Install Apache Beam on Own Server.

Additionally, performing a search on this website can help you. Also, we have YouTube Videos.

Take The Conversation Further ...

We'd love to know your thoughts on this article.
Meet the Author over on Twitter to join the conversation right now!

If you want to Advertise on our Article or want a Sponsored Article, you are invited to Contact us.

Contact Us

Subscribe To Our Free Newsletter

Get new posts by email:

Please Confirm the Subscription When Approval Email Will Arrive in Your Email Inbox as Second Step.

Search this website…

 

Popular Articles

Our Homepage is best place to find popular articles!

Here Are Some Good to Read Articles :

  • Cloud Computing Service Models
  • What is Cloud Computing?
  • Cloud Computing and Social Networks in Mobile Space
  • ARM Processor Architecture
  • What Camera Mode to Choose
  • Indispensable MySQL queries for custom fields in WordPress
  • Windows 7 Speech Recognition Scripting Related Tutorials

Social Networks

  • Pinterest (22.1K Followers)
  • Twitter (5.8k Followers)
  • Facebook (5.7k Followers)
  • LinkedIn (3.7k Followers)
  • YouTube (1.3k Followers)
  • GitHub (Repository)
  • GitHub (Gists)
Looking to publish sponsored article on our website?

Contact us

Recent Posts

  • FaaS Versus PaaS Deployment: What You Should Know May 18, 2022
  • What Is A Digital Media Consultancy? May 17, 2022
  • How Artificial Intelligence (AI) Is Changing The Way We Play Bingo May 16, 2022
  • Why You Need A Big Data Consultant May 15, 2022
  • The Connection Between AI And Online Slots May 13, 2022

About This Article

Cite this article as: Abhishek Ghosh, "The Fundamentals of Microservices," in The Customize Windows, February 13, 2021, May 20, 2022, https://thecustomizewindows.com/2021/02/the-fundamentals-of-microservices/.

Source:The Customize Windows, JiMA.in

This website uses cookies. If you do not want to allow us to use cookies and/or non-personalized Ads, kindly clear browser cookies after closing this webpage.

Read Privacy Policy.

PC users can consult Corrine Chorney for Security.

Want to know more about us? Read Notability and Mentions & Our Setup.

Copyright © 2022 - The Customize Windows | dESIGNed by The Customize Windows

Copyright  · Privacy Policy  · Advertising Policy  · Terms of Service  · Refund Policy