Explore topic-wise InterviewSolutions in .

There are MANY useful scenarios for leveraging the power of JWT-

• Authentication 

Authentication is one of the most common scenarios for USING JWT, specifically in microservices architecture (but not limited to it). In microservices, the oauth2 server generates a JWT at the time of login and all subsequent requests can include the JWT AccessToken as the means for authentication. Implementing Single Sign-On by sharing JWT b/w different applications hosted in different domains.

• Information Exchange 

JWT can be signed, using public/private key pairs, you can be sure that the senders are who they say they are. Hence JWT is a good way of sharing information between two parties. An example use case could be - 

1. GENERATING Single Click Action Emails e.g. Activate your account, delete this comment, ADD this item to favorites, Reset your password, etc. All required information for the action can be put into JWT.
2. Timed sharing of a file download using a JWT link. Timestamp can be part of the claim, so when the server time is past the time-coded in JWT, the link will automatically expire. 

Important Tools and LIBRARIES for testing Spring-based Microservices are - 

• JUnit 

the standard test runners 

• TestNG 

the next generation test runner 

• Hemcrest 

declarative MATCHERS and assertions 

• Rest-assured 

for writing REST Api DRIVEN end to end tests 

• Mockito 

for mocking dependencies 

• Wiremock 

for stubbing thirdparty services 

• Hoverfly 

Create API simulation for end-to-end tests. 

• Spring Test and Spring BOOT Test 

for writing Spring Integration Tests - includes MockMVC, TestRestTemplate, Webclient like features. 

• JSONassert 

An assertion library for JSON. 

• Pact 

The Pact family of FRAMEWORKS provide support for Consumer Driven Contracts testing. 

• Selenium 

Selenium automates browsers. Its used for end-to-end automated ui testing. 

• Gradle 

Gradle helps build, automate and deliver software, fastr. 

• IntelliJ IDEA 

IDE for Java Development 

• Using spring-boot-starter-test 
  • We can just add the below dependency in project’s build.gradle 
  • testCompile('org.springframework.boot:spring-boot-starter-test')

This starter will import two spring boot test modules spring-boot-test & spring-boot-test- autoconfigure as well as Junit, AssertJ, Hamcrest, Mockito, JSONassert, Spring Test, Spring Boot Test and a number of other useful libraries.

OAuth2.0 is a delegation protocol where the Client (Mobile App or web app) does not need to know about the credentials of RESOURCE Owner (end-user). 

Oauth2 defines four roles. 

1. Resource Owner - The person or the application that owns the data to be shared. When a resource owner is a person, it is called as an end-user.
2. Resource Server - The application that HOLDS the protected resources. It is usually a microservice.
3. Authorization Server - the application that verifies the identity of the resource owner (users/clients). These server ISSUES access TOKENS after obtaining the authorization.
4. Client - the application that MAKES a request to Resource Server on behalf of Resource Owner. It could be a mobile app or a web app (like stackoverflow).

There are 3 parts in every JWT claim - Header, Claim and Signature. These 3 parts are separated by a dot. The ENTIRE JWT is encoded in Base64 format. 

JWT = {header}.{payload}.{signature} 

A typical JWT is shown here for reference. 

Encoded JSON Web Token

Entire JWT is encoded in Base64 format to make it compatible with HTTP protocol. Encoded JWT looks like the FOLLOWING:

Decoded JSON Web Token 

Header 

Header contains algorithm information e.g. HS256 and type e.g. JWT 

Claim 

claim part has an expiry, ISSUER, user_id, scope, roles, client_id etc. It is encoded as a JSON object. You can add custom attributes to the claim. This is the information that you want to exchange with the third party. 

Signature 

Signature is typically a one way hash of (header + payload), is calculated using HMAC SHA256 algorithm. The secret used for signing the claim should be kept private. Pubic/private key can also be used to encrypt the claim instead of using symmetric cryptography. 

Basic Authentication is natively supported by almost all servers and clients, even Spring security has very good SUPPORT for it and its configured out of the box. But it is not a good fit for Microservices due to many reasons, including - 

1. We need credentials (username and password) every time we authenticate. This may be fine where all the participants can share the secrets SECURELY, but Users may not be willing to share their credentials with all the applications.
2. There is no distinction between Users and Client Apps (an application that is making a request). In a realistic environment, we often need to know if a real user is making a request or a client app is making a request (for inter-service communication).
3. It only covers authentication. what about scopes, Authorizations? Basic Auth does not support adding additional attributes in the authentication headers. There is no concept of Tokens in basic auth.
4. Performance reasons for BCrypt Matching. Passwords are often stored in the database using one-way hash i.e. Bcrypt, it TAKES a lot of cpu cycles depending upon the strength (a.k.a. log rounds in BCrypt) to compare the user’s plain password with db saved bcrypt password, so it may not be efficient to match password on every request. The larger the strength parameter the more work will have to be done (exponentially) to hash the passwords. If you set the strength to 12, then in total 212 iterations will be done in Bcrypt Logic. Usually, 4-8 passwords can be matched per second on a T2.Micro instance on Amazon AWS instance. See BCryptPasswordEncoder for more info.
5. If we use Basic Auth for a mobile application client, then we might have to store user’s credentials on the device to ALLOW REMEMBER me feature. This is quite risky as anyone getting access to the device may steal the plain credentials.

Swagger is a very good open-source tool for documenting   APIs PROVIDED by microservices. It provides very easy to USE INTERACTIVE documentation.

By the use of swagger annotation on REST endpoint, api documentation can be auto-generated and exposed over the web interface. An internal and external team can use web interface, to see the list of APIs and their inputs & error CODES. They can even invoke the endpoints directly from web interface to get the results.

Swagger UI is a very powerful tool for your microservices consumers to help them understand the set of endpoints provided by a given microservice.

Caching is a technique of performance improvement for getting query results from a service. It helps minimize the calls to network, database, etc. We can use caching at multiple levels in microservices architecture - 

1. Server-Side Caching - DISTRIBUTED caching software like Redis/MEMCACHE/etc are used to cache the results of business operations. The cache is distributed so all instances of a microservice can see the values from the shared cache. This type of caching is opaque to clients.
2. Gateway Cache - central API gateway can cache the query results as per business needs and provide improved performance. This way we can achieve caching for multiple services at one place. Distributed caching software like Redis or Memcache can be used in this case.
3. Client-Side Caching - We can set cache-headers in HTTP response and allow clients to cache the results for a pre-defined time. This will drastically reduce the load on servers since the client will not make REPEATED calls to the same resource. Servers can inform the clients when information is changed, thereby any changes in the query result can also be handled. E-Tags can be used for client-side load BALANCING. If the end client is a microservice itself, then Spring Cache support can be used to cache the results locally. 

Microservices Architecture can become cumbersome & unmanageable if not done properly. There are best practices that help design a resilient & highly scalable system. The most important ones are 

• Partition correctly 

Get to know the domain of your business, that's very very important. Only then you will be able to define the bounded context and partition your microservice correctly based on business capabilities. 

• DevOps culture 

Typically, everything from continuous integration all the way to continuous delivery and deployment should be automated. Otherwise,   a big pain to manage a large fleet of microservices. 

• Design for stateless operations 

We never know where a new instance of a particular microservice will be spun up for scaling out or for handling failure, so maintaining a state inside service instance is a very bad idea. 

• Design for failures 

Failures are inevitable in distributed systems, so we must design our system for handling failures gracefully. failures can be of different types and must be dealt with accordingly, for example - 

1. Failure could be transient due to inherent brittle nature of the network, and the next retry may succeed. Such failures must be protected using retry operations.
2. Failure may be due to a hung service which can have cascading effects on the calling service. Such failures must be protected using Circuit Breaker Patterns. A fallback mechanism can be used to provide degraded functionality in this case.
3. A single component may fail and affect the health of the entire system, bulkhead pattern must be used to prevent the entire system from failing. 

• Design for versioning 

We should try to make our services backward compatible, explicit versioning must be used to cater different versions of the RESt endpoints. 

• Design for asynchronous communication b/w services 

Asynchronous communication should be preferred over synchronous communication in inter microservice communication. One of the biggest advantages of using asynchronous messaging is that the service does not block while waiting for a response from another service. 

• Design for eventual consistency 

Eventual consistency is a consistency model used in distributed computing to achieve high availability that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will RETURN the last updated value. 

• Design for idempotent operations 

SINCE networks are brittle, we should always design our services to accept repeated calls without any side effects. We can add some unique identifier to each request so that service can ignore the duplicate request sent over the network due to network failure/retry logic. 

• Share as little as possible 
  

In monolithic applications, sharing is considered to be a best practice but that's not the case with Microservices. Sharing results in a violation of Bounded Context Principle, so we shall refrain from creating any single unified shared model that works across microservices. For example, if different services need a common CUSTOMER model, then we should create one for each microservice with just the required FIELDS for a given bounded context rather than creating a big model class that is shared in all services. 

The more dependencies we have between services, the harder it is to isolate the service changes, making it difficult to make a change in a single service without affecting other services. Also, creating a unified model that works in all services brings complexity and ambiguity to the model itself, making it hard for anyone to understand the model.

In a way are want to violate the DRY principle in microservices architecture when it comes to domain models.

In a microservices architecture, each microservice shall own its private DATA which can only be accessed by the outside world through owning service. If we START sharing microservice’s private datastore with other services, then we will violate the principle of Bounded Context. 

Practically we have three approaches -

1. Database server PER microservice - Each microservice will have its own database server instance. This approach has the overhead of maintaining database instance and its replication/backup, hence its rarely used in a practical environment. 
2. SCHEMA per microservice - Each microservice owns a private database schema which is not accessible to other services. Its most preferred approach for RDMS database (MySql, Postgres, ETC.)
3. Private Table per microservice - Each microservice owns a set of tables that must only be accessed by that service. It’s a logical separation of data. This approach is mostly used for the hosted database as a service solution (Amazon RDS).

@HystrixCommand annotation provides attribute ignoreExceptions that can be USED to PROVIDE a list of ignored exceptions.

Code

• import com.netflix.hystrix.contrib.javanica.annotation.HystrixCommand;
• import org.springframework.beans.factory.annotation.Autowired;
• import org.springframework.cloud.client.ServiceInstance;
• import org.springframework.cloud.client.loadbalancer.LoadBalancerClient; 
• import org.springframework.stereotype.Service;
• import org.springframework.web.client.RestTemplate; 
• import java.net.URI;

@Service

@Autowired

@Autowired

@HystrixCommand(fallbackMethod = "reliable", ignoreExceptions = IllegalStateException.class, MissingServletRequestParameterException.class, TypeMismatchException.class)

ServiceInstance instance = loadBalancer.choose("product-service"); URI uri = URI.create("HTTP://product-service/product/recommended"); return this.restTemplate.getForObject(uri, String.class);}

In the above example, if the ACTUAL method call throws IllegalStateException, MissingServletRequestParameterException or TypeMismatchException then hystrix will not trigger the fallback logic (reliable method), instead the actual EXCEPTION will be wrapped inside HystrixBadRequestException and re-thrown to the caller. It is taken care by javanica library under the hood.

Using config-server, it's possible to refresh the configuration on the fly. The configuration changes will only be picked by Beans that are declared with @RefreshScope annotation.

The following code illustrates the same. The PROPERTY message is defined in the config-server and changes to this property can be made at runtime without restarting the microservices. 

1 @RefreshScope makes it possible to dynamically reload the configuration for this bean.

There are different ways to handle the versioning of your REST api to allow older consumers to STILL consume the older endpoints. The ideal practice is that any nonbackward compatible change in a given REST endpoint shall lead to a NEW versioned endpoint. 

Different mechanisms of versioning are: 

• Add VERSION in the URL itself
• Add version in API request header 

Most common approach in versioning is the URL versioning itself. A versioned URL looks like the following: 

Versioned URL 

• https://<HOST>:<port>/api/v1/...
• https://<host>:<port>/api/v2/...

As an API developer you must ensure that only backward-compatible changes are accommodated in a single version of URL. Consumer-Driven-Tests can help identify potential issues with API UPGRADES at an early stage.

Martin Fowler introduced the concept of "smart endpoints & dumb pipes" while describing microservices architecture.

To give context, one of the main characteristic of a   based system is to build small utilities and connect them using pipes. For example, a very popular way of finding all java processes in LINUX system is Command pipeline in Unix shell ps elf | grep java

Here two commands are separated by a pipe, the pipe’s job is to forward the output of the FIRST command as an input to the second command, NOTHING more.   like a dumb pipe which has no business logic except the routing of data from one utility to another.

In his article Martin Fowler compares Enterprise Service Bus (ESB) to ZeroMQ/RabbitMQ, ESB is a pipe but has a lot of logic INSIDE it while ZeroMQ has no logic except the persistence/routing of messages. ESB is a fat layer that does a lot of things like - security checks, routing, business flow & validations, data transformations, etc. So ESB is a kind of smart pipe that does a lot of things before passing data to next endpoint (service). Smart endpoints & dumb pipes advocate an exactly opposite idea where the communication channel should be stripped of any business-specific logic and should only distribute messages between components. The components (endpoints/services) should do all the data validations, business processing, security checks, etc on those incoming messages. 

Microservices team should follow the principles and protocols that WORLDWIDE web & Unix is built on.

The bulkhead implementation in Hystrix limits the number of CONCURRENT calls to a component/service. This way, the number of resources (typically threads) that are waiting for a reply from the component/service is limited.

Let's assume we have a fictitious web e-commerce application as shown in the figure below. The WebFront communicates with 3 different components using remote network calls (REST over HTTP). 

• Product catalogue Service
• Product Reviews Service
• Order Service

Now let's SAY due to some problem in Product Review Service, all requests to this service start to hang (or timeout), eventually causing all request handling threads in WebFront Application to hang on waiting for an answer from Reviews Service. This would make the entire WebFront Application non-responsive. The resulting behavior of the WebFront Application would be same if request volume is high and Reviews Service is taking TIME to respond to each request.

The Hystrix Solution

Hystrix’s implementation for bulkhead pattern would limit the number of concurrent calls to components and would have saved the application in this case by GRACEFULLY degrading the FUNCTIONALITY. Assume we have 30 total request handling threads and there is a limit of 10 concurrent calls to Reviews Service. Then at most 10 request handling threads can hang when calling Reviews Service, the other 20 threads can still handle requests and use components Products and Orders Service. This will approach will keep our WebFront responsive even if there is a failure in Reviews Service. 

Let's say we want to HANDLE service to service failure GRACEFULLY without using the Circuit Breaker pattern. The naive approach would be to wrap the   REST call in a try-catch clause. But Circuit Breaker does a lot more than try-catch can not accomplish - 

1. Circuit Breaker does not even try calls once the failure threshold is reached, doing so reduces the number of network calls. Also, a number of THREADS consumed in making faulty calls are freed up.
2. Circuit breaker provides fallback method execution for gracefully degrading the behavior. Try catch approach will not do this out of the box without additional boiler plate code.
3. Circuit Breaker can be configured to use a limited number of threads for a particular host/API, doing so brings all the benefits of bulkhead design pattern. 

So instead of WRAPPING service to service calls with try/catch clause, we must use the circuit breaker pattern to make our system resilient to failures.

Hystrix library makes our distributed system resilient (adaptable & quick to recover) to failures. It 

PROVIDES three main features: 

• Latency and fault-tolerance 

It helps stop cascading failures, PROVIDE decent fallbacks and graceful degradation of service functionality to confine failures. It works on the idea of fail-fast and rapid RECOVERY. Two different options namely THREAD isolation and Semaphore isolation are available for use to confine failures. 

• Real-time OPERATIONS 

Using real-time metrics, you can remain alert, make decisions, affect changes and see results. 

• Concurrency 

Parallel execution, concurrent aware request caching and finally automated batching through request collapsing improves the concurrency performance of your application. 

More information on Netflix hystrix library: 

• https://github.com/Netflix/Hystrix/
• https://github.com/Netflix/Hystrix/wiki#principles
• https://github.com/Netflix/Hystrix/wiki/How-it-Works

HYSTRIX is Netflix implementation for CIRCUIT breaker pattern, that ALSO employs bulkhead design pattern by operating each circuit breaker within its own thread pool. It also collects many useful metrics about the circuit breaker’s internal state, including -

1. Traffic volume.
2. Request volume.
3. Error percentage.
4. Hosts reporting
5. Latency percentiles.
6. Successes, failures, and rejections.

All these metrics can be aggregated using another Netflix OSS project called Turbine. Hystrix dashboard can be used to VISUALIZE these aggregated metrics, providing excellent visibility into the overall health of the distributed system.
Hystrix can be used to specify the fallback method for execution in case the ACTUAL method call fails. This can be useful for graceful degradation of functionality in case of failure in remote invocation. 

1) Enable Circuit Breaker in main application 

2) Using HystrixCommand fallback method execution 

1. Using @HystrixCommand annotation, we specify the fallback method to execute in case of exception. 
2. fallback method should have the same signature (return type) as that of the original method. This method provides a graceful fallback behavior while the circuit is in the open or half-open state.

Strangulation is used to slowly decommission an older system and migrate the functionality to a newer version of microservices. 

Normally one endpoint is Strangled at a time, slowly replacing all of them with the newer implementation. Zuul Proxy (API Gateway) is a useful tool for this because we can use it to handle all traffic from clients of the old endpoints, but redirect only selected requests to the new ones. 

Let’s take an example use-case: 

first:

legacy:

1. Paths in /first/** have been EXTRACTED into a new service with an EXTERNAL URL http://first.example.com 
2. legacy app is mapped to handle all REQUEST that do not match any other patterns (/first/**). 

This configuration is for API Gateway (zuul reverse proxy), and we are strangling selected endpoints /first/ from the legacy app hosted at http://legacy.example.com slowly to newly created microservice with external URL http://first.example.com

Config first bootstrap and discovery first bootstrap are two different approaches for using Spring Cloud Config client in Spring Cloud-powered microservices. Let’s discuss both of them:

Config First Bootstrap 

This is the default behavior for any spring BOOT APPLICATION where Spring Cloud Config client is on the classpath. When a config client starts up it binds to the Config Server using the bootstrap configuration property and initializes Spring Environment with remote property sources.

• Config-first approach 

The only configuration that each microservice (except config-server) needs to provide is the following: 

• File:-  /src/main/resources/bootstrap.yml 
• spring.cloud.config.uri: http://localhost:8888 
• In config-first approach, even the eureka-server can fetch its own configuration from config-server. Point worth noting down here is that config-server must be the first service to boot up in the entire ecosystem, because each service will fetch its configuration from config-server. 

Discovery First Bootstrap 

If you are using Spring Cloud Netflix and Eureka Service Discovery then you can have Config Server register with the Discovery Service and let all CLIENTS get access to config server via discovery service. 

• Discovery-first approach 

This is not the default configuration in Spring Cloud applications, so we need to manually enable it using the below property in bootstrap.yml 

The benefit of this approach is that now config-server can change its host/port without other microservices KNOWING about it since each microservice can get the configuration via eureka service now. The downside of this approach is that an EXTRA network round trip is required to locate the service registration at app startup. 

1. Synchronous communication over the network that is likely to fail is a potential CANDIDATE for circuit breaker.
2. A circuit breaker is a valuable place for monitoring, any CHANGE in the breaker state should be logged so as to enable deep monitoring of microservices. It can easily troubleshoot the root CAUSE of failure.
3. All places where a degraded functionality can be acceptable to the caller if the actual server is struggling/down. 

Benefits:-

1. The circuit breaker can prevent a single service from failing the entire system by tripping off the circuit to the faulty microservice. 
2. The circuit breaker can help to offload REQUESTS from a struggling server by tripping the circuit, thereby giving it a time to recover. 
3. In PROVIDING a fallback mechanism where a stale data can be provided if real service is down.

Circuit Breaker wraps the original remote calls inside it and if any of these calls fails, the failure is counted. When the service dependency is healthy and no issues are detected, the circuit breaker is in Closed state. All invocations are passed through to the remote service. 

If the failure count exceeds a specified threshold within a specified time period, the circuit trips into the Open State. In the Open State, calls always FAIL immediately without even invoking the actual remote call. The following factors are considered for tripping the circuit to Open State - 

• An Exception thrown (HTTP 500 error, can not connect)
• Call takes longer than the configured timeout (default 1 second)
• The internal thread pool (or semaphore depending on configuration) used by hystrix for the COMMAND execution rejects the execution DUE to exhausted resource pool. 

After a predetermined period of time (by default 5 SECONDS), the circuit transitions into a half-open state. In this state, calls are again attempted to the remote dependency. Thereafter the successful calls transition the circuit breaker back into the closed state, while the failed calls return the circuit breaker into the open state.

Microservices often need to make remote network calls to another microservices running in a different process. Network calls can fail due to many reasons, including-

1. Brittle nature of the network itself
2. Remote process is hung or
3. Too much traffic on the TARGET microservices than it can handle

This can lead to cascading failures in the calling service due to threads being blocked in the hung remote calls. A circuit breaker is a piece of software that is used to solve this problem. The basic idea is very simple - wrap a potentially failing remote call in a circuit breaker object that will monitor for failures/timeouts. Once the failures reach a certain threshold, the circuit breaker trips, and all further calls to the circuit breaker return with an error, without the PROTECTED call being made at all. This mechanism can protect the cascading effects of a single component failure in the system and provide the option to gracefully downgrade the functionality.

A typical use of circuit breaker in microservices architecture LOOKS like the following diagram-

Typical Circuit Breaker Implementation 

Here a REST client calls the Recommendation Service which further communicates with Books Service using a circuit breaker call wrapper. As soon as the books-service API calls starts to fail, circuit breaker will trip (open) the circuit and will not make any further call to book-service until the circuit is CLOSED again. 

Martin Fowler has beautifully explained this phenomenon in detail on his blog. 

Martin Fowler on Circuit Breaker Pattern : https://martinfowler.com/bliki/CircuitBreaker.html 

There are two main components in Eureka project: eureka-server and eureka-client. 

• Eureka Server 

The central server (ONE PER zone) that acts as a service registry. All microservices register with this eureka server during app bootstrap. 

• Eureka Client 

Eureka also comes with a Java-based client component, the eureka-client, which makes interactions with the service MUCH easier. The client also has a built-in load balancer that does basic round-robin load balancing. Each microservice in the distributed ecosystem much include this client to communicate and register with eureka-server.

• Typical use case for Eureka 

There is usually one eureka server cluster per REGION (US, Asia, Europe, Australia) which knows only about instances in its region. Services register with Eureka and then send heartbeats to renew their leases every 30 seconds. If the service can not renew their lease for a few times, it is taken out of server registry in about 90 seconds. The registration information and the renewals are replicated to all the eureka nodes in the cluster. The CLIENTS from any zone can look up the registry information (happens every 30 seconds) to locate their services (which could be in any zone) and make remote calls. 

Eureka clients are built to handle the failure of one or more Eureka servers. Since Eureka clients have the registry cache information in them, they can operate reasonably well, even when all of the eureka servers go down.

If you have 3 different ENVIRONMENTS (develop/stage/production) in your project setup, then you need to create three different config storage projects. So in total, you will have four projects: 

• config-server 

It is the config-server that can be deployed in each environment. It is the Java Code WITHOUT configuration storage. 

• config-dev 

It is the git storage for your development configuration. All configuration related to each MICROSERVICES in the development environment will FETCH its config from this storage. This project has no Java code, and t is meant to be used with config-server.

• config-qa 
  

Same as config-dev but its meant to be used only in qa environment.

• Config-prod
  • Same as config-dev, but meant for production environment.
  • So depending upon the environment, we will use config-server with either config-dev, config-qa or config-prod.

Servers come and go in a cloud environment, and new instances of same services can be deployed to cater increasing load of requests. So it becomes absolutely essential to have service registry & discovery that can be queried for finding address (host, port & protocol) of a given server. We may also need to locate servers for the purpose of client-side load balancing (Ribbon) and handling failover gracefully (Hystrix). 

Spring Cloud solves this problem by providing a few ready-made solutions for this challenge. There are mainly two options available for the service discovery - Netflix Eureka Server and Consul. Let's discuss both of these briefly:

Netflix Eureka Server 

Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers. The main features of Netflix Eureka are:

1. It provides service-registry.
2. zone aware service lookup is possible.
3. eureka-client (used by microservices) can cache the registry locally for faster lookup. The client also has a built-in load balancer that does basic round-robin load balancing. 

Spring Cloud provides two dependencies - eureka-server and eureka-client. Eureka server dependency is only REQUIRED in eureka server’s build.gradle 

• build.gradle - Eureka Server 
• compile('org.springframework.cloud:spring-cloud-starter-netflix-eureka-server')

On the other hand, each microservice need to include the eureka-client dependencies to ENABLES eureka discovery. 

build.gradle - Eureka Client (to be included in all microservices) compile('org.springframework.cloud:spring-cloud-starter-netflix-eureka-client').

Eureka server provides a basic dashboard for monitoring various instances and their health in the service registry. The ui is written in freemarker and provided out of the box without any extra CONFIGURATION. Screenshot for Eureka Server looks like the following. 

It contains a list of all services that are registered with Eureka Server. Each server has information like zone, host, port, and protocol. 

Consul Server 

It is a REST-based tool for dynamic service registry. It can be used for REGISTERING a new service, locating a service and health checkup of a service. 

You have the option to choose any one of the above in your spring cloud-based distributed APPLICATION. In this book, we will focus more on the Netflix Eureka Server option.

In the microservices architecture, it is possible that due to service boundaries, a lot of TIMES you need to update one or more entities on the state change of one of the entities. In that case, one needs to publish a message and new event gets created and appended to already executed events. In case of FAILURE, one can replay all events in the same sequence and you will get the DESIRED state as required. You can think of event sourcing as your bank account statement.

You will start your account with initial money. Then all of the credit and debit events happen and the latest state is generated by calculating all of the events one by one. In a case where events are too many, the application can create a periodic SNAPSHOT of events so that there isn’t any  need to replay all of the events again and again.

One should avoid sharing database between microservices, instead APIs should be exposed to perform the change.

If there is any dependency between microservices then the service holding the data should PUBLISH MESSAGES for any change in the data for which other services can CONSUME and update the local state.

If consistency is required then microservices should not maintain local state and instead can pull the data whenever required from the SOURCE of truth by making an API call.

An API Gateway is a service which sits in front of the exposed APIs and acts as an entry point for a group of MICROSERVICES. Gateway also can hold the minimum logic of routing calls to microservices and also an aggregation of the response.

• A gateway can also authenticate requests by verifying the identity of a user by routing each and every request to authentication service before routing it to the microservice with authorization details in the token.
• Gateways are also responsible to LOAD balance the requests.
• API Gateways are responsible to rate limit a certain type of request to save itself from blocking several kinds of attacks etc.
• API Gateways can whitelist or blacklist the source IP Addresses or given domains which can INITIATE the call.
• API Gateways can also provide plugins to cache certain type of API RESPONSES to boost the performance of the application.

In a production environment, you don’t just deal with the application code/application server. You need to deal with API Gateway, Proxy Servers, SSL terminators, Application Servers, Database Servers, Caching Services, and other dependent services.

As in modern microservice ARCHITECTURE where each microservice runs in a separate container, deploying and managing these containers is very challenging and might be error-prone.

Container orchestration solves this problem by managing the life cycle of a container and allows us to AUTOMATE the container deployments.

It also helps in scaling the application where it can easily bring up a few containers. Whenever there is a high load on the application and once the load goes down. it can scale down as well by BRINGING down the containers. It is helpful to adjust cost based on requirements.

Also in some cases, it takes care of internal networking between services so that you need not make any extra EFFORT to do so. It also helps us to replicate or deploy the docker images at runtime without worrying about the resources. If you need more resources, you can configure that in orchestration services and it will be available/deployed on production servers within MINUTES.

As container based deployment involves a single image per microservice, it is a bad idea to bundle the configuration along with the image.

This approach is not at all SCALABLE because we might have multiple environments and also we might have to TAKE care of geographically distributed DEPLOYMENTS where we might have different configurations as well.

Also, when there are application and cron application as part of the same codebase, it might need to take additional care on production as it might have repercussions how the crons are architected.

To solve this, we can put all our configuration in a centralized config service which can be queried by the application for all its configurations at the runtime. Spring CLOUD is one of the example services which provides this facility.

It also helps to secure the information, as the configuration might have passwords or access to reports or database access controls. Only trusted parties should be allowed to access these details for security reasons.

Docker helps in many ways for microservices architecture.

1. In a microservice architecture, there can be many different services written in different languages. So a developer might have to SETUP few services ALONG with its dependency and platform requirements. This becomes difficult with the growing number of services in an ECOSYSTEM. However, this becomes very easy if these services run inside a Docker container.
2. Running services inside a container also give a similar setup across all the environments, i.e development, staging and production.
3. Docker also helps in SCALING along with container orchestration.
4. Docker helps to upgrade the underlying language very easily. We can save many man-hours.
5. Docker helps to onboard the engineers fast.
6. Docker also helps to reduce the dependencies on IT Teams to set up and manage the different kind of environment REQUIRED.

Logging is a very important aspect of any application. If we have done proper logging in an application, it becomes easy to support other aspects of the application as WELL. Like in order to debug the ISSUES / in order to understand what business logic might have been executed, it becomes very critical to log important details.

Ideally, you should follow the following PRACTICES for logging.

• In a microservice architecture, each request should have a unique VALUE (correlationid) and this value should be passed to each and every microservice so the correlationid can be logged across the services. Thus the requests can be traced.
• Logs generated by all the services should be aggregated in a single location so that while searching becomes easier. Generally, PEOPLE use ELK stack for the same. So that it becomes easy for support persons to debug the issue.

There are mainly two WAYS to achieve AUTHENTICATION in microservices architecture.

• Centralized sessions

All the microservices can use a CENTRAL session store and user authentication can be achieved. This approach works but has many drawbacks as well. Also, the centralized session store should be protected and services should connect securely. The application needs to manage the state of the user, so it is called stateful session.

• Token-based authentication/authorization

In this approach, unlike the traditional way, information in the form of token is held by the clients and the token is passed along with each request. A server can check the token and verify the VALIDITY of the token like expiry, etc. Once the token is validated, the IDENTITY of the user can be obtained from the token. However, encryption is required for security reasons. JWT(JSON web token) is the new open standard for this, which is widely used. Mainly used in stateless applications. Or, you can use OAuth based authentication mechanisms as well.

It is an important design DECISION. The communication between services might or might not be necessary. It can happen synchronously or asynchronously. It can happen SEQUENTIALLY or it can happen in parallel. So, once we have decided what should be our communication mechanism, we can decide the technology which suits the best.

Here are some of the EXAMPLES which you can consider.

• Communication can be done by using some queuing service LIKE rabbitmq, activemq and kafka. This is called asynchronous communication.
• Direct API calls can also be made to microservice. With this approach, interservice DEPENDENCY increases. This is called synchronous communication.
• Webhooks to push data to connected clients/services.

This is a very interesting question. In monolith where HTTP Request waits for a response, the PROCESSING happens in memory and it makes sure that the transaction from all such modules work at its best and ensures that everything is done according to expectation. But it becomes challenging in the case of microservices because all services are running independently, their datastores can be independent, REST Apis can be deployed on different endpoints. Each service is doing a  bit without knowing the context of other microservices.

In this case, we can use the following measures to MAKE sure we are able to trace the errors easily.

1. Services should log and aggregators push logs to centralized logging servers. For example, use ELK Stack to analyze.
2. Unique value per client request(correlation-id) which should be logged in all the microservices so that errors can be traced on a central logging server.
3. One should have good MONITORING in place for each and EVERY microservice in the ecosystem, which can record application metrics and health checks of the services, TRAFFIC pattern and service failures.

This is related to the automation for cross-cutting concerns. We can standardize some of the concerns like monitoring strategy, deployment strategy, review and commit strategy, branching and merging strategy, testing strategy, code structure STRATEGIES etc.

For standards, we can FOLLOW the 12-factor application guidelines. If we follow them, we can definitely achieve great productivity from day one. We can also containerize our application to utilize the latest DevOps themes like dockerization. We can use mesos, MARATHON or kubernetes for orchestrating docker images. Once we have dockerized source code, we can use CI/CD pipeline to deploy our newly created codebase. Within that, we can add mechanisms to test the applications and make sure we measure the required METRICS in order to deploy the code. 

We can use strategies like blue-green deployment or canary deployment to deploy our code so that we know the impact of code which might go live on all of the servers at the same time. We can do AB testing and make sure that things are not broken when live. In order to reduce a burden on the IT TEAM, we can use AWS / Google cloud to deploy our solutions and keep them on autoscale to make sure that we have enough resources available to serve the traffic we are receiving.

In real time, it happens that a particular service is causing a downtime, but the other services are functioning as per mandate. So, under such conditions, the particular service and its dependent services get affected DUE to the downtime.

In order to solve this ISSUE, there is a concept in the microservices architecture pattern, called the circuit breaker. Any service calling remote service can call a proxy layer which acts as an electric circuit breaker. If the remote service is slow or down for ‘N’ attempts then proxy layer should fail fast and keep checking the remote service for its availability again. As well as the calling services should handle the errors and provide retry logic. Once the remote service RESUMES then the services starts working again and the circuit becomes complete.

This way, all other functionalities WORK as expected. Only one or the dependent services get affected.

It is a very subjective QUESTION, but with the best of my knowledge I can SAY that it should be based on the following criteria.

• Business functionalities that change TOGETHER in bounded context
• Service should be TESTABLE independently.
• Changes can be done WITHOUT affecting clients as well as dependent services.
• It should be small enough that can be maintained by 2-5 developers.
• Reusability of a service

When you are implementing microservices architecture, there are some challenges that you need to deal with every SINGLE microservices. Moreover, when you think about the interaction with each other, it can create a lot of challenges. As well as if you pre-plan to overcome some of them and standardize them across all microservices, then it happens that it also becomes easy for developers to MAINTAIN services.

Some of the most challenging things are testing, debugging, security, version management, communication ( sync or async ), state maintenance ETC. Some of the cross-cutting CONCERNS which should be standardized are monitoring, logging, performance improvement, deployment, security etc.

Spring team has an integrated number of battle-tested open-source projects from companies like Pivotal, Netflix into a Spring PROJECT known as Spring Cloud. Spring Cloud provides libraries & tools to quickly BUILD some of the common design patterns of a distributed system, including the following:

Spring Cloud makes it really easy to DEVELOP, deploy and operate JVM applications for the Cloud.

ACID is an acronym for four primary attributes namely atomicity, consistency, isolation, and durability ensured by the database transaction manager. 

• Atomicity 

In a transaction involving two or more entities, either all of the records are committed or none are. 

• Consistency 

A database transaction must change affected data only in allowed ways following specific rules including constraints/triggers etc. 

• Isolation 

Any transaction in progress (not yet committed) must REMAIN ISOLATED from any other transaction. 

• Durability 

Committed records are saved by a database such that even in case of a failure or database restart, the data is available in its correct state. 

In a distributed SYSTEM involving multiple databases, we have two options to achieve ACID compliance: 

1. One way to achieve ACID compliance is to use a two-phase commit (a.k.a 2PC), which ensures that all INVOLVED services must commit to transaction completion or all the transactions are rolled back.
2. Use eventual consistency, where multiple databases owned by different microservices become eventually consistent USING asynchronous messaging using messaging protocol. Eventual consistency is a specific form of weak consistency. 

2 Phase Commit should ideally be discouraged in microservices architecture due to its fragile and complex nature. We can achieve some level of ACID compliance in distributed systems through eventual consistency and that should be the right approach to do it.

The deployment scenario becomes complex when there are database CHANGES during the upgrade. There can be two different SCENARIOS: 1. database change is backward compatible (e.g. adding a new table column) 2. database change is not compatible with an older version of the application (e.g. RENAMING an existing table column) 

1. Backward compatible change: This scenario is easy to IMPLEMENT and can be fully automated using Flyway. We can add the script to create a new column and the script will be executed at the time of deployment. Now during blue/green deployment, two versions of the application (say v1 and v2) will be connected to the same database. We need to make sure that the newly added columns allow null values (btw that’s PART of the backward compatible change). If everything goes well, then we can switch off the older version v1, else application v2 can be taken off. 
2. Non-compatible database change: This is a tricky scenario, and may require manual intervention in-case of rollback. Let's say we want to rename first_name column to fname in the database. Instead of directly renaming, we can create a new column fname and copy all existing values of first_name into fname column, keeping the first_name column as it is in the database. We can defer non-null checks on fname to post-deployment success. If the deployment goes successful, we need to migrate data written to first_name by v1 to the new column (fname) manually after bringing down the v1. If the deployment fails for v2, then we need to do the otherwise. 

Complexity may be much more in a realistic production app, such discussions are beyond the scope of this book.

As the name suggests, zero-downtime deployments do not bring outage in a production environment. It is a clever way of deploying your changes to production, where at any given point in time, at least one service will remain available to customers.

• Blue-green deployment 
  

One way of achieving this is blue/green deployment. In this approach, two versions of a single microservice are deployed at a time. But only one version is taking real requests. Once the newer version is tested to the required satisfaction level, you can switch from older version to newer version.

You can run a smoke-test suite to verify that the functionality is running correctly in the newly deployed version. Based on the results of smoke-test, newer version can be released to BECOME the live version.

• Changes required in CLIENT code to handle zero-downtime 

Lets say you have two instances of a service running at the same time, and both are registered in Eureka registry. Further, both instances are deployed using two distinct hostnames: 

  eureka.instance.hostname: ticketBooks-service -green.example.com

Now the client app that needs to make api calls to books-service may look like below: 

Now, when ticketBooks-service-green.example.com goes down for upgrade, it gracefully shuts down and delete its entry from Eureka registry. But these changes will not be reflected in the ClientApp until it fetches the registry again (which happens every 30 seconds). So for upto 30 seconds, ClientApp’s @LoadBalanced RestTemplate may send the requests to ticketBooks-service-green.example.com even if its down. 

To fix this, we can use Spring RETRY support in Ribbon client-side load balancer. To enable Spring Retry, we need to follow the below steps: 

Add spring-retry to build.gradle dependencies 

Now enable spring-retry mechanism in ClientApp using @EnableRetry annotation, as shown below: 

Once this is done, Ribbon will automatically configure itself to use retry logic and any failed request to ticketBooks-service-green.example.com com will be retried to next available instance (in round-robins fashion) by Ribbon. You can customize this behaviour using the below properties: 

API Gateway is a special class of microservices that meets the need of a single client application (such as android app, web app, angular JS app, iPhone app, etc) and provide it with single entry point to the backend resources (microservices), providing cross-cutting concerns to them such as security, monitoring/metrics &AMP; resiliency. 

Client Application can access tens or hundreds of microservices concurrently with each request, aggregating the response and transforming them to meet the client application’s needs. Api Gateway can use a client-side load BALANCER library (Ribbon) to distribute load across instances based on round-robin FASHION. It can ALSO do protocol translation i.e. HTTP to AMQP if necessary. It can handle security for protected resources as well.

Features of API Gateway

1. Spring Cloud DiscoveryClient integration
2. Request Rate Limiting (available in Spring Boot 2.x)
3. Path Rewriting
4. Hystrix Circuit Breaker integration for resiliency

Spring Boot along with Spring CLOUD is a very good option to start building microservices using Java LANGUAGE. There are a lot of modules available in Spring Cloud that can provide boiler plate code for different design patterns of microservices, so Spring Cloud can really speed up the development process. Also, Spring boot provides out of the box support to embed a servlet container (tomcat/jetty/undertow) INSIDE an executable jar (uber jar), so that these jars can be run directly from the command line, eliminating the need of deploying war files into a servlet container. 

You can also use Docker container to ship and DEPLOY the entire executable package onto a cloud environment. Docker can also help eliminate "works on my machine" problem by providing LOGICAL separation for the runtime environment during the development phase. That way you can gain portability across on-premises and cloud environment.

Cloud-Native Applications (NCA) is a style of application development that encourages easy adoption of best practices in the area of continuous delivery and distributed software development. These applications are designed specifically for a cloud computing architecture (AWS, Azure, CloudFoundary, etc).

DevOps, continuous delivery, microservices, and containers are the key concepts in developing cloud-native applications.

Spring Boot, Spring Cloud, Docker, Jenkins, Git are a few tools that can help you write Cloud-Native Application without much effort.

• Microservices

It is an architectural APPROACH for developing a distributed system as a COLLECTION of small services. Each service is responsible for a specific business capability, runs in its own process and communicates via HTTP REST API or messaging (AMQP).

• DevOps

It is a collaboration between software developers and IT operations with a GOAL of constantly delivering high-quality software as per customer needs.

• Continuous Delivery

Its all about automated delivery of low-risk small changes to production, constantly. This makes it possible to collect FEEDBACK faster.

• Containers

Containers (e.g. Docker) offer logical isolation to each microservices thereby eliminating the problem of "run on my MACHINE" forever. It’s much faster and efficient compared to Virtual Machines.

There is no right answer to this question, there could be a release every ten minutes, every hour or once a week. It all depends on the EXTENT of automation you have at a different level of the software development lifecycle - build automation, test automation, deployment automation and monitoring. And of course on the business requirements - how small low-risk changes you care making in a single release.

In an IDEAL world where boundaries of each microservices are clearly defined (bounded context), and a given service is not affecting other microservices, you can easily achieve multiple deployments a DAY without major complexity.

Examples of deployment/release frequency

1. Amazon is on record as making changes to production every 11.6 seconds on average in May of 2011.
2. Github is well known for its aggressive engineering practices, deploying code into production on an average 60 times a day.
3. Facebook releases to production twice a day.
4. Many Google services see releases multiple times a week, and almost everything in Google is DEVELOPED on mainline.
5. Etsy Deploys More Than 50 Times a Day.

In Orchestration, we rely on a central system to control and call other Microservices in a certain fashion to complete a given task. The central system maintains the state of each step and sequence of the overall workflow. In Choreography, each Microservice WORKS like a State Machine and reacts based on the input from other parts. Each service knows how to react to different events from other systems. There is no central command in this case.

Orchestration is a tightly coupled APPROACH and is an anti-pattern in a microservices architecture. Whereas, Choreography’s loose coupling approach should be adopted where-ever possible.

Example

Let’s say we want to develop a microservice that will send product recommendation email in a fictitious e-shop. In ORDER to send Recommendations, we NEED to have access to user’s order history which lies in a different microservices. 

In Orchestration approach, this new microservice for recommendations will make synchronous calls to order service and fetch the relevant data, then based on his past purchases we will calculate the recommendations. Doing this for a million users will become cumbersome and will tightly couple the two microservices. 

In Choreography approach, we will use event-based Asynchronous communication where whenever a user makes a purchase, an event will be published by order service. Recommendation service will listen to this event and start building user recommendation. This is a loosely coupled approach and highly scalable. The event, in this case, does not tell about the ACTION, but just the data.

1. You must use asynchronous communication while handling HTTP POST/PUT (anything that modifies the data) requests, using some reliable queue mechanism (RabbitMQ, AMQP, etc.) 
2. It's fine to use SYNCHRONOUS communication for Aggregation pattern at API Gateway Level. But this aggregation should not include any business logic other than aggregation. Data VALUES must not be transformed at Aggregator, otherwise, it DEFEATS the purpose of Bounded Context. In Asynchronous communication, events should be published into a Queue. Events contain data about the domain, it should not tell what to do (action) on this data. 
3. If MICROSERVICE to microservice communication still requires synchronous communication for GET operation, then seriously reconsider the partitioning of your microservices for bounded context, and create some TASKS in backlog/technical debt.

Microservices are OFTEN integrated using a simple protocol like REST over HTTP. Other communication protocols can also be used for INTEGRATION like AMQP, JMS, Kafka, etc.

The communication protocol can be broadly DIVIDED into two categories- synchronous communication and asynchronous communication.

• Synchronous Communication

RestTemplate, WebClient, FeignClient can be used for synchronous communication between two microservices. Ideally, we should minimize the number of synchronous calls between microservices because networks are brittle and they INTRODUCE latency. Ribbon - a client-side load balancer can be used for better utilization of resource on the top of RestTemplate. Hystrix circuit breaker can be used to handle partial failures gracefully without a cascading effect on the entire ecosystem. DISTRIBUTED commits should be avoided at any cost, instead, we shall opt for eventual consistency using asynchronous communication.

• Asynchronous Communication
  

In this type of communication, the client does not wait for a response, instead, it just sends the message to the message broker. AMQP (like RabbitMQ) or Kafka can be used for asynchronous communication across microservices to achieve eventual consistency.