MICROSERVICES AND ARCHITECTURE
Vivek Yadav
Arth3.0 Learner|| MERN || Docker || Linux || AWS || python || ML || JS || Kubernetes || Jenkins || Ansible
What Are Microservices?
Microservices?are an architectural style that structure applications as a collection of loosely connected services, making it easier for developers to build and scale apps. The microservices architectural approach differs from the?conventional monolithic style, which treats software development as a?single unit.?
The microservices method breaks down software development into smaller, independent “chunks,” where each chunk executes a particular service or function. Microservices utilize integration, API management, and cloud deployment technologies.?
How microservices works
Microservices are a set of services that act together to make a whole application operate. This architecture utilizes APIs to pass information, such as user queries or a?data stream, from one service to another.
How the underlying software works, or which hardware the service is built upon, depends solely on the team who built the service. This makes both communicating between teams and upgrading services very dynamic—even reactive—allowing a software company or team to be?more resilient?in its development.
Kubernetes?has helped advance the cause of microservices, though it not a necessary building block. The rise of?cloud computing ?and networked computers has done two things:
In the case of microservices, the user’s machine may be responsible for basic processing, but it is mostly responsible for sending and receiving network calls to other computers.
Whenever you use an application, it’s reasonable to assume that there are five other computers, give or take, that just turned on in order to power your experience. In the case of something like Facebook or Uber, it may be more reasonable to expect another 10,000 computers are actively processing information to enhance the user experience.
Microservices are often considered a logical evolution of? Service oriented architecture (SOA), but there are?clear difference between the two.
Why Use Microservices?
Microservices bring multiple benefits to teams like yours:
Monolithic architecture vs microservice architecture
The monolithic architecture pattern has been the architectural style used in the past, pre-Kubernetes and cloud services days.
In a monolithic architecture, the software is a single application distributed on a CD-ROM, released once a year with the newest updates. Examples are Photoshop CS6 or Microsoft 2008.
That style was the standard way of building software. But as tech has evolved, so too the architectural style must advance. In an age of Kubernetes, and CI/CD workflows, the monolithic architecture encounters many limitations—companies need to push to microservices.
Characteristics of a monolithic architecture:
Microservices in the Cloud (AWS and Azure)
Various platforms automate many of the processes associated with microservices in the cloud. However, there are two developers should consider:??
领英推荐
Once up and running, these systems require little human intervention from developers unless debugging problems occur.?
AWS
Amazon pioneered microservices with service-based architecture many years ago. Now its AWS platform, available to developers worldwide, takes cloud microservices to the next level. Using this system, developers can break down monolithic architecture into individual microservices via three patterns: API-driven, event-driven, and data streaming. The process is much quicker than doing it manually, and development teams can create highly scalable applications for clients.
Azure
Azure is another cloud-based system that makes microservices easier. Developers use patterns like circuit breaking to improve reliability and security for individual services rather than tinkering with the whole app.
Azure lets you create APIs for microservices for both internal and external consumption. Other benefits include authentication, throttling, monitoring, and caching management. Like AWS, Azure is an essential tool for teams that want to improve agile software development.?
Benefits Of Microservices
Simpler to deploy
Deploy in literal pieces without affecting other services.
Simpler to understand
Code is easier to follow since the function is isolated and less dependent.
Reusable across business
Share small services like payment or login systems across the business.
Faster defect isolation
When a test fails or service goes down, isolate it quickly.
Minimized risk from change
Avoid locking in technologies or languages - change on the fly with minimal risk.
Examples of Microservices
Netflix has a widespread architecture that has evolved from monolithic to SOA. It receives more than one billion calls every day, from more than 800 different types of devices, to its streaming-video API. Each API call then prompts around five additional calls to the backend service.
Amazon has also migrated to microservices. They get countless calls from a variety of applications – including applications that manage the web service API as well as the website itself – which would have been simply impossible for their old, two-tiered architecture to handle.
The Future of Microservice Architecture
Whether or not microservice architecture becomes the preferred style of developers in future, it’s clearly a potent idea that offers serious benefits for designing and implementing enterprise applications. Many developers and organizations, without ever using the name or even labeling their practice as SOA, have been using an approach toward leveraging APIs that could be classified as microservices.
We’ve also seen a number of existing technologies try to address parts of the segmentation and communication problems that microservices aim to resolve. SOAP does well at describing the operations available on a given endpoint and where to discover it via WSDLs. UDDI is theoretically a good step toward advertising what a service can do and where it can be found.