MicroService Project Interview Question
MicroService Project Interview Question
MicroService Project Interview Question
I have seen many devs fumble over this question. After all, they're getting asked
this question when interviewing for a microservices architect role, so
acknowledging its cons can be a little tricky. Here are some good answers:
They need heavy architecture set up � The system is distributed, the architecture
is heavily involved.
They need excessive planning for handling operations overhead � You need to be
ready for operations overhead if you are planning to use a microservices
architecture.
They have autonomous staff selection � Skilled professionals are needed who can
support microservices that are distributed heterogeneously
Reports and dashboards are mainly used to monitor and upkeep microservices. There
are multiple tools that help to serve this purpose. Reports and dashboards can be
used to:
Find out the services which are impacted whenever changes in a component occur.
This is a very common microservices interview question which you should be ready
for! There are plenty of pros that are offered by a microservices architecture.
Here are a few of them:
For server configuration, you have to configure the client first. Once that is
done, the server fires up a client which is used to find other servers. The Eureka
server, by default, uses the Client configuration to find the peer server.
It is one of the most important features, which helps you to access the current
state of an application that is running in a production environment. There are
multiple metrics which can be used to check the current state. They also provide
endpoints for RESTful web services which can be simply used to check the different
metrics
REFCARDZ
GUIDES
ZONES
Agile
AI
Big Data
More
? by
Arnab Roy
Like (16)
Comment (0)
Save
Tweet
A survey by Nginx shows that 36% of enterprises are currently using microservices,
while another 26% are doing research on how to implement them. So now could be a
good time to get into microservice development. Read on for an overview of some of
the most common microservices interview questions.
For typical use cases, Spring Cloud provides the out of the box experiences and a
sets of extensive features mentioned below:
Routing.
It is one of the most important features, which helps you to access the current
state of an application that is running in a production environment. There are
multiple metrics which can be used to check the current state. They also provide
endpoints for RESTful web services which can be simply used to check the different
metrics.
package com.gkatzioura.security.securityendpoints.config;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import
org.springframework.security.config.annotation.web.configuration.WebSecurityConfigu
rerAdapter;
@Configuration
@Override
http.authorizeRequests()
.antMatchers("/welcome").permitAll()
.anyRequest().authenticated()
.and()
.formLogin()
.permitAll()
.and()
.logout()
.permitAll();
Whenever you are creating a Java application, deployment can be done via two
methods:
Undertow � A flexible and prominent web server that uses small single handlers to
develop a web server.
PACT is an open source tool. It helps in testing the interactions between consumers
and service providers. However, it is not included in the contract, increasing the
reliability of the application. The consumer service developer starts by writing a
test which defines a mode of interaction with the service provider. The test
includes the provider�s state, the request body, and the response that is expected.
Based on this, PACT creates a stub against which the test is executed. The output
is stored in a JSON file