Nitin Agrawal
Contact -
  • Home
  • Interviews
    • Secret Receipe
    • InterviewFacts
    • Resume Thoughts
    • Daily Coding Problems
    • BigShyft
    • CompanyInterviews >
      • InvestmentBanks >
        • ECS
        • Bank Of America
        • WesternUnion
        • WellsFargo
      • ProductBasedCompanies >
        • CA Technologies
        • Model N India
        • Verizon Media
        • Oracle & GoJek
        • IVY Computec
        • Nvidia
        • ClearWaterAnalytics
        • ADP
        • ServiceNow
        • Pubmatic
        • Expedia
        • Amphora
        • CDK Global
        • CDK Global
        • Epic
        • Sincro-Pune
        • Whiz.AI
        • ChargePoint
      • ServiceBasedCompanies >
        • Altimetrik
        • ASG World Wide Pvt Ltd
        • Paraxel International & Pramati Technologies Pvt Ltd
        • MitraTech
        • Intelizest Coding Round
        • EPAM
    • Interviews Theory
  • Programming Languages
    • Java Script >
      • Tutorials
      • Code Snippets
    • Reactive Programming >
      • Code Snippets
    • R
    • DataStructures >
      • LeetCode Problems
      • AnagramsSet
    • Core Java >
      • Codility
      • Program Arguments OR VM arguments & Environment variables
      • Java Releases
      • Threading >
        • ThreadsOrder
        • ProducerConsumer
        • Finalizer
        • RaceCondition
        • Executors
        • Future Or CompletableFuture
      • Important Points
      • Immutability
      • Dictionary
      • URL Validator
    • Julia
    • Python >
      • Decorators
      • String Formatting
      • Generators_Threads
      • JustLikeThat
    • Go >
      • Tutorial
      • CodeSnippet
      • Go Routine_Channel
      • Suggestions
    • Methodologies & Design Patterns >
      • Design Principles
      • Design Patterns >
        • TemplatePattern
        • Adapter Design Pattern
        • Decorator
        • Proxy
        • Lazy Initialization
        • CombinatorPattern
        • RequestChaining
        • Singleton >
          • Singletons
  • Frameworks
    • Apache Velocity
    • Spring >
      • Spring Boot >
        • CustomProperties
        • ExceptionHandling
        • Issues
      • Quick View
    • Rest WebServices >
      • Interviews
      • Swagger
    • Cloudera BigData >
      • Ques_Ans
      • Hive
      • Apache Spark >
        • ApacheSpark Installation
        • SparkCode
        • Sample1
        • DataFrames
        • RDDs
        • SparkStreaming
        • SparkFiles
    • Integration >
      • Apache Camel
    • Testing Frameworks >
      • JUnit >
        • JUnit Runners
      • EasyMock
      • Mockito >
        • Page 2
      • TestNG
    • Blockchain >
      • Ethereum Smart Contract
      • Blockchain Java Example
    • Microservices >
      • Messaging Formats
      • Design Patterns
    • AWS >
      • Honeycode
    • Dockers >
      • GitBash
      • Issues
  • Databases
    • MySql
    • Oracle >
      • Interview1
      • SQL Queries
    • Elastic Search
  • Random issues
    • TOAD issue
    • Architect's suggestions
  • Your Views
Micro-services is another buzzword in the market today. I am observing many architects favour micro-services architecture for the applications. I am saying the same for past many months but headless architects & tech geeks are eager to risk the
projects to get their hands on any new technology or process like 'Microservices' & still such organisations wonder why their projects are not generating the profits, just observe your leadership, CEO or Architects or Managers once.
​But one must understand that it is not silver bullet to solve all your problems in the application. It is dual edged sword rather, which can make your job extremely easy or can make your life a hell.
​If you are planning to study micro-services, then go ahead & have a look on this but before planning to use it in your application & before designing your application around micro-services, have a good look on the application requirements, how you are planning to handle the changes in the application, what kind of changes you are expecting, what kind of performance you are expecting from your application etc. After such thorough study, if you feel that micro-services will benefit
​you, then go for this.
​It is like distributing the responsibilities, services across many nodes or modules or servers, i.e. it is like distributed architecture of your monolithic application. Which you may be knowing is not something easy to develop & orchestrate, it needs separate level of planning, designing & believe it or not, Microservices need a lot of resources to work.
​So, once you are sure then yes go ahead & use micro-services architecture in your application.
​www.nginx.com/blog/introduction-to-microservices/
https://martinfowler.com/articles/microservices.html
https://martinfowler.com/microservices/
Service Discovery
5 patterns to make your microservice fault-tolerant
itnext.io/5-patterns-to-make-your-microservice-fault-tolerant-f3a1c73547b3 
Below Image is taken from
media-exp1.licdn.com/dms/image/C5622AQGYPj99vKT_BA/feedshare-shrink_800/0/1634711018400?e=1637798400&v=beta&t=E6XcUu1C-1gQFSPlnIn7bHgiEsiCMcyz007W0qE9uvM
Picture
 Zuul or Spring Cloud Gateway or NGinx

​
Microservices Choreography vs Orchestration: The Benefits of Choreography - Solace

Top Microservices Tools To Manage Microservices | Edureka

​Monolithic vs Microservices Architecture | by Neeraj Kushwaha | Feb, 2022 | Medium
4 Microservice Frameworks in Comparison, Streaming Example Included (itemis.com)
​

 Below image is taken from book :             Microservice Architecture
                                                                Aligning Principles, Practices, and Culture
written by -                Irakli Nadareishvili, Ronnie Mitra,Matt McLarty, and Mike Amundsen

 It is a 1-2 days read book with around 120 pages to study, though total pages are 146.
I will not say that everyone should read it to understand the microservices or it is a great book to understand the right way to
implement the microservices.
I don't think that there is one right or wrong way to create any application/product, though many people, even from big
companies like Sapient, Wells Fargo, Bank Of America etc claim during the interviews that they know that correct way.
But we all know that what chances can be with such people.
 So I am suggesting this small book to read once to get one or two perspectives about microservices, which can help you to
decide better. Means don't consider any one book is giving you the right receipe for what you want to do, but there is also no 
​harm to know about various ways also.
Picture
Powered by Create your own unique website with customizable templates.