Authentic techniques of authentication in microservices (original) (raw)

International Journal of Current Advanced Research

The rudimentary approach for developing software has been the monolithic way. Monolithic approach is still good for small scale teams and projects, nevertheless once scalability, flexibility and other requirements like fast development, short time to market, wider team alliance, and so on becomes gradually critical to accomplish business competitiveness, monolithic halts being profitable. This is where the Microservices architecture comes to rescue. Microservices is responsible for an intensive, scoped and modular tactic for application design. Microservices are small, autonomous services that work together. [1] It can be well elaborated using keywords: 'Faster development and Speed to production'. Microservices are deceptively termed to be code of limited length. Conversely, microservices are a piece of code which performs a single task and performs it soundly. They are independent in failure i.e. failure of a single component does not force the entire system to breakdown at once. The term micro indicates the services to be lightweight and which cannot be further divided into sub tasks and performs one task solely with minimal dependency on other services. They are independently scalable as well. The most perplexing part of microservices is defining the granularity of the services. Security in microservices is one of the least explored topics. This paper explores the various vulnerabilities in security and also presents the various methods deployed for providing authentication and authorization in microservi microservices depends on the idea of loose coupling and high

Sign up for access to the world's latest research.

checkGet notified about relevant papers

checkSave papers to use in your research

checkJoin the discussion with peers

checkTrack your impact