Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Foyzul Karim, profile picture
Uploaded byFoyzul Karim
PPTX, PDF480 views

Microservices: A developer's approach

The document discusses microservices, an architectural style that enables the development of applications as a suite of small, independently deployable services that enhance maintainability and scalability. It explores the historical context of microservices, the design and building blocks involved, and the reasons for their growing necessity in modern software development, particularly with advancements in cloud computing and containerization. The author invites further inquiries and engagement through various social media platforms.

Softwareā—¦
Download to read offline
Microservices A Developerā€™s Approach
Topics ā€¢ What is Microservices ā€¢ Why we need Microservices ā€¢ Design a single service ā€¢ Building blocks of a Microservice System ā€¢ Whatā€™s next
@Me ā€¢ Foyzul Karim ā€¢ Started journey on 2009 ā€¢ Details on LinkedIn [linkedin.com/in/foyzul] ā€¢ Love to make videos [youtube.com/foyzulkarim] ā€¢ Love to contribute open source [github.com/foyzulkarim] ā€¢ Love to contribute on Facebook [facebook.com/foyzulsacademy]
Microservices Soā€¦ What is it?
Brief history ā€¢ The term "microservice" was discussed at a workshop of software architects near Venice in May 2011 to describe what the participants saw as a common architectural style that many of them had been recently exploring. ā€¢ In May 2012, the same group decided on "microservices" as the most appropriate name. James Lewis presented some of these ideas as a case study in March 2012 at 33rd Degree in Krakow in Microservices - Java, the Unix Way as did Fred George about the same time. ā€¢ Adrian Cockcroft at Netflix, describing this approach as "fine grained SOA" was pioneering the style at web scale as were many of the others mentioned in this article - Joe Walnes, Daniel Terhorst-North, Evan Botcher and Graham Tackley. ā€¢ Article link: https://martinfowler.com/articles/microservices.html
Microservices ā€¢ In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. ā€¢ These services are built around business capabilities and independently deployable by fully automated deployment machinery. ā€¢ There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. -- James Lewis and Martin Fowler (2014) [https://martinfowler.com/articles/microservices.html]
https://martinfowler.com/articles/microservices/images/sketch.png Single executable project Project 1 Project 2 Project 3
Characteristics of a Microservice System ā€¢ Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are ā€¢ Highly maintainable and testable ā€¢ Loosely coupled ā€¢ Independently deployable ā€¢ Organized around business capabilities ā€¢ Owned by a small team ā€¢ The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack.
Why we need Microservices? And why now? Why we didnā€™t use this architecture 15 years ago?
Why we need Microservices? Why now? ā€¢ Single vendor lockdown era is over ā€¢ Different database for different purpose ā€¢ Different programming stack for different purpose ā€¢ Different software architecture for different purpose ā€¢ Scaling is not more multiplying the whole server ā€¢ Containers (Lxc, Lxd, Docker etc.) ā€¢ Orchestrators (Kubernetes) ā€¢ Cloud computing era is in full swing ā€¢ Can choose different cloud service in different microservice ā€¢ We donā€™t have luxury to go offline for a minute now a days ā€¢ No more outage because of a problematic service
Design a single micro-service How do we design a single service?
Designing a single micro-service ā€¢ Define the domain boundaries ā€¢ Follow Single Responsibility Principal in every level ā€¢ Select appropriate tech stack ā€¢ Choose programming stack ā€¢ Choose database ā€¢ Database can only be accessed by itā€™s parent service ā€¢ Expose the api endpoints to be consumed by other services ā€¢ Should independently handle the request ā€¢ Adapt the architecture for the whole microservices system Service DB
Microservices System What are the building blocks of a microservices system
Building blocks of a Microservices System ā€¢ Service to service communication ā€¢ Client to service communication ā€¢ Service discovery ā€¢ Service security ā€¢ Service monitoring ā€¢ Service containerization ā€¢ Service orchestration ā€¢ Continuous integration ā€¢ Continuous delivery
Service to service communication ā€¢ Point to point communication ā€¢ HTTP request ā€¢ gRPC request ā€¢ Asynchronous message-based communication ā€¢ Queue ā€¢ Service Bus
Http / gRPC request
Service ServiceService Messaging system
Client to service communication ā€¢ API Manager / API Gateways ā€¢ Directly call to the service
API API API API EventBus API GatewayClient
API API API API EventBus Client
Service discovery ā€¢ Mainly applicable for container based architecture ā€¢ Register the service into a service registry
API API API API EventBus Client/APIM Service registry Name: product, Ip: 10.0.0.15 Name: customer, Ip: 10.0.0.16 Name: sales, Ip: 10.0.0.17 Name: identity, Ip: 10.0.0.18 Get product service detail
Service security ā€¢ Authentication server ā€¢ Handles different types of authentication ā€¢ Token based ā€¢ Cookie based ā€¢ Authorization server ā€¢ Fully functional RBAC management system ā€¢ Returns true/false depending on the resource request
Service monitoring ā€¢ Paid ā€¢ Application insight ā€¢ Papertrail ā€¢ Datadog ā€¢ Free ā€¢ ELK (self hosted)
Service containerization ā€¢ Multiple service to use multiple types of resources ā€¢ Different operating system (Linux, Windows etc.) ā€¢ Different programming language (C#, Python, JavaScript etc.) ā€¢ Different database (SQL Server, MySQL, MongoDB, ElasticSearch etc.) ā€¢ Different package versions ā€¢ We need the runtime and a thin OS layer to execute the system calls ā€¢ Containers here to rescue ā€¢ Pack the service (containerize) ā€¢ Run it anywhere ā€¢ Docker
Service orchestration ā€¢ How to build the containers in multiple environments ā€¢ How to run the containers in multiple environments ā€¢ How to monitor the containers after deployment ā€¢ How to troubleshoot the containers ā€¢ Kubernetes, Docker Compose etc.
Where to go next? ā€¢ Build one from scratch
Questions? Send email to foyzulkarim@gmail.com Send message to ā€œFoyzulā€™s Academyā€ Facebook page