Why Microservices ?

By -
Problem statement: What is microservices?

1. Microservices is a method of developing software applications as a unit of independently deployable, small, modular services in which each service runs a unique process and communicates through a well defined, light weight mechanism to serve a business goal.

2. microservice gives developer the freedom to independently develop and deploy services.

3. microservices is a variant/type of Service Oriented Architecture (SOA) that structures an application as collection (group of individual service) of loosely coupled services.

4. Easy integration and automatic deployment (using open source continuous integration tools like Jenkins, Hudson)

5. When change is required in a certain part of the application, only the related service can be modified and redeployed — no need to modify and redeploy the entire application

6. Better fault isolation: If one microservice fails, the other will continue to work.

7. Easy to scale & integrate with third-party services.

8. Simple to understand & modify the service for developers, thus can help a new team member become productive quickly.

  • How the microservice communicates with each other ?
It uses HTTP / REST Webserives with JSON. REST(Representational State Transfer) is useful integration method
  • How Microservice Architecture Works?
  1. Object Oriented Programming (OOP)—a modern programming paradigm (see also SOLID)
  2. Web service / API—a way to expose the functionality of your application to others, without a user interface
  3. Service Oriented Architecture (SOA)—a way of structuring many related applications to work together, rather than trying to solve all problems in one application
  4. Systems—in the general sense, meaning any collection of parts that can work together for a wider purpose
  5. Single Responsibility Principle (SRP)—the idea of code with one focus
  6. Interface Segregation Principle (ISP)—the idea of code with defined boundaries.

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more