Intro to Microservices
•Download as PPTX, PDF•
2 likes•198 views
A presentation the describes the evolution and nature of mciroservices for use is distributed, service oriented architecture
Report
Share
Report
Share
Recommended
Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.
The document discusses continuous delivery at Coolblue. It outlines their back office development, focus on creating great software, and approach to continuous delivery. Their continuous delivery approach includes: releasing code as soon as possible after it is merged; taking small, frequent steps; and making it easy to correct mistakes. Key aspects of their approach include heavy testing, code quality practices like reviews, automating processes as much as possible, and monitoring systems. The takeaways are that the most important things are having great team members and putting software live quickly while also having a forgiving environment for mistakes.
Deployment Nirvana
This document discusses the challenges faced by the author in deploying and scaling a microservices architecture. Some of the initial problems encountered were services flapping and resulting downtime during deployments. Various solutions tried included service registries, routing layers, and versioning at the service and inter-service level. However, complexity grew and developer experience suffered. The author advocates for simpler deployments that prioritize engineer productivity through better tooling while still enabling rolling deployments and isolation of services.
Coolblue Behind the Scenes | Jeffrey Simons - The UX nerd and you.
This document discusses how designers and engineers can work together effectively. It notes that designers and developers often have different perspectives that can cause conflicts. However, through developing a shared understanding of each other's roles and a shared vision of adding value to the product, these conflicts can be resolved. Specific recommendations include using a common language without jargon, collaborative techniques like pairing, and focusing project work on solving business problems and delivering value to users through user stories.
Agile tour agile development
Tom Klaasen has 10 years of experience developing software using Java/J2EE and more recently Ruby on Rails and iOS. He co-founded 10to1 in 2006 which uses an agile development process with 4 highly skilled passionate developers. They focus on communication through daily deployments and meetings with users, prioritizing developing workable applications over extensive testing or documentation. Their agile approach is influenced by the conventions of Ruby on Rails and aims to be flexible rather than following rigid rules.
Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015
This document summarizes Phil Calçado's experience with microservices at SoundCloud over three years. It describes how SoundCloud moved to microservices for rapid provisioning and deployment. This created monitoring challenges as services became more distributed. SoundCloud developed its own telemetry tools to address these issues. The document also discusses lessons learned, such as standardizing dashboards and operations, and how initial microservice implementations at SoundCloud were imperfect but improved over time through experience.
Week7
The document provides an overview and agenda for a Ruby mid-term review session. It discusses using Cucumber for behavior driven development and testing with MiniTest. It also demonstrates how to write Cucumber features and step definitions, and integrate Cucumber tests with Jeweler and Travis.
Coolblue Behind the Scenes | Pat Hermens - On the shoulders of giants.
The document discusses the evolution of Coolblue's legacy system called Vanessa over the past 15 years as the company has grown from processing around 1 order per day to over 12,000 orders per day currently. As Vanessa aged it became more difficult to maintain and adapt to new business needs. Coolblue transitioned Vanessa to a microservices architecture using C# and RabbitMQ for messaging to address challenges around agility, reliability, and integrating new systems. Key parts of the new architecture include using RabbitMQ for background jobs, intra-service communication, and sharing data between new and legacy systems through message triggers.
Pragmatic Microservices
One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.
This session takes a pragmatic approach to microservices, and compares them to the alternatives at different stages of company evolution. Using examples both from Google and eBay as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful rearchitecture to microservices.
Recommended
Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.
The document discusses continuous delivery at Coolblue. It outlines their back office development, focus on creating great software, and approach to continuous delivery. Their continuous delivery approach includes: releasing code as soon as possible after it is merged; taking small, frequent steps; and making it easy to correct mistakes. Key aspects of their approach include heavy testing, code quality practices like reviews, automating processes as much as possible, and monitoring systems. The takeaways are that the most important things are having great team members and putting software live quickly while also having a forgiving environment for mistakes.
Deployment Nirvana
This document discusses the challenges faced by the author in deploying and scaling a microservices architecture. Some of the initial problems encountered were services flapping and resulting downtime during deployments. Various solutions tried included service registries, routing layers, and versioning at the service and inter-service level. However, complexity grew and developer experience suffered. The author advocates for simpler deployments that prioritize engineer productivity through better tooling while still enabling rolling deployments and isolation of services.
Coolblue Behind the Scenes | Jeffrey Simons - The UX nerd and you.
This document discusses how designers and engineers can work together effectively. It notes that designers and developers often have different perspectives that can cause conflicts. However, through developing a shared understanding of each other's roles and a shared vision of adding value to the product, these conflicts can be resolved. Specific recommendations include using a common language without jargon, collaborative techniques like pairing, and focusing project work on solving business problems and delivering value to users through user stories.
Agile tour agile development
Tom Klaasen has 10 years of experience developing software using Java/J2EE and more recently Ruby on Rails and iOS. He co-founded 10to1 in 2006 which uses an agile development process with 4 highly skilled passionate developers. They focus on communication through daily deployments and meetings with users, prioritizing developing workable applications over extensive testing or documentation. Their agile approach is influenced by the conventions of Ruby on Rails and aims to be flexible rather than following rigid rules.
Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015
This document summarizes Phil Calçado's experience with microservices at SoundCloud over three years. It describes how SoundCloud moved to microservices for rapid provisioning and deployment. This created monitoring challenges as services became more distributed. SoundCloud developed its own telemetry tools to address these issues. The document also discusses lessons learned, such as standardizing dashboards and operations, and how initial microservice implementations at SoundCloud were imperfect but improved over time through experience.
Week7
The document provides an overview and agenda for a Ruby mid-term review session. It discusses using Cucumber for behavior driven development and testing with MiniTest. It also demonstrates how to write Cucumber features and step definitions, and integrate Cucumber tests with Jeweler and Travis.
Coolblue Behind the Scenes | Pat Hermens - On the shoulders of giants.
The document discusses the evolution of Coolblue's legacy system called Vanessa over the past 15 years as the company has grown from processing around 1 order per day to over 12,000 orders per day currently. As Vanessa aged it became more difficult to maintain and adapt to new business needs. Coolblue transitioned Vanessa to a microservices architecture using C# and RabbitMQ for messaging to address challenges around agility, reliability, and integrating new systems. Key parts of the new architecture include using RabbitMQ for background jobs, intra-service communication, and sharing data between new and legacy systems through message triggers.
Pragmatic Microservices
One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.
This session takes a pragmatic approach to microservices, and compares them to the alternatives at different stages of company evolution. Using examples both from Google and eBay as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful rearchitecture to microservices.
The "Why", "What" and "How" of Microservices
This document discusses microservices and alternatives to monolithic architectures. It begins by outlining the costs of software maintenance for monoliths and reasons why architectures need to change to adapt quickly. Alternatives like SOA are discussed, but microservices are presented as a way to break applications into fine-grained, independent services. However, the document cautions that simply breaking a monolith into smaller pieces does not automatically achieve decoupling, and improper use of microservices could result in even greater complexity. Autonomous services with explicit boundaries and asynchronous communication are emphasized as important characteristics to achieve decoupling.
Microservices music city code v2
- Microservices are an architectural style that structures an application as a collection of small, independent services that communicate with each other, often using RESTful API's. Each service focuses on doing a small job and is organized around business capabilities.
- The benefits of microservices include improved modularity, resilience, scalability, and autonomy for teams. Complexity is shifted outward so that services are easy to understand, enhance, test and deploy independently.
- Implementing microservices involves organizing code around business capabilities, following best practices like SOLID principles, domain-driven design, and contract-first development. It also requires automating delivery pipelines, monitoring, and abstracting service boundaries through techniques like API management and message
Surviving in a Microservices environment -abridged
Many presentations on Microservices offer a high-level view; rarely does one hear what it’s like to work in such an environment. Individual services are somewhat trivial to develop, but now you suddenly have countless others to track. You’ll become obsessed over how they communicate. You’ll have to start referring to the whole thing as “the Platform”. You will have to take on some considerable DevOps work and start learning about deployment pipelines, metrics, and logging.
Don’t panic. In this presentation we’ll discuss what we learned over the past four years by highlighting our mistakes. We’ll examine what a development lifecycle might look like for adding a new service, developing a feature, or fixing bugs. We’ll see how team communication is more important than one might realize. Most importantly, we’ll show how - while an individual service is simple - the infrastructure demands are now much more complicated: your organization will need to introduce and become increasingly dependent on various technologies, procedures, and tools - ranging from the ELK stack to Grafana to Kubernetes. Lastly, you’ll come away with the understanding that your resident SREs will become the most valued members of your team.
Microservices for Mortals by Bert Ertman at Codemotion Dubai
With popular poster children such as Netflix and Amazon, Microservices based architecture seems to be the killer approach to 21st century architectures. But are they only for Hollywood Coders pioneering on the bleeding edge of our profession? Or are they ready to be used for your projects and your customers? I will go over the benefits, but more so the pitfalls, of using a Microservices based architecture. What impact does it have on your organization, your applications, on dealing with scale and failures, and how do you prevent your landscape from becoming an unmaintainable nightmare.
Minimal Viable Architecture - Silicon Slopes 2020
This presentation introduces the idea of a "Minimal Viable Architecture". As a company and product evolves, its architecture should evolve as well. We talk about the different phases of a product -- from the idea phase, to the starting phase, scaling phase, and optimizing phase. For each phase, we discuss the goals and constraints on the business, and we suggest an appropriate software architecture to match. Throughout the presentation, we use examples from eBay, Google, StitchFix, and others.
Service Architectures at Scale
How do effective large-scale service ecosystems work? Keynote Presentation at Istanbul Tech Talks 2018
How to Design Services
* Systems of record
* Interface specification
* Interface backward / forward compatibility
Service Ecosystems
* Layered services
* "Standardization" through encouragement
* Vendor-customer relationships between teams
Operating and Deploying Services
* Data Migration
* Automated Pipelines
* Incremental Deployment
* Feature Flags
SACon 2019 - Surviving in a Microservices Environment
Many presentations on microservices offer a high-level view of the architecture; rarely do you hear what it’s like to work in such an environment. Stephen Pember shares his experience migrating from a monolith to microservices across several companies, highlighting the mistakes made along the way and offering advice.
Microserces Architecture
The document discusses microservice architecture, providing definitions and comparisons to monolithic and SOA architectures. It describes microservices as independently deployable services that work together to provide business capabilities. The benefits of microservices include evolutionary design, auto-scaling, and increased system resilience. Some challenges are also outlined, such as distributed logging and transaction spanning.
Microservices for Mortals
Microservices is the new popular kid on the block. Crowd pleaser at many conferences. With popular poster children such as Netflix and Amazon it seems to be the killer approach to 21st century architectures, right? But is this stuff only for Hollywood Coders pioneering on the bleeding edge of our profession? Or is this stuff ready to be used for your projects and your customers? This presentation is a warning. Microservices don't fix broken organizations and distributed computing is still hard. I will go over the benefits, but more so the pitfalls, of using a Microservices based architecture. What impact does it have on your applications, on dealing with scale and failures, and how do you prevent your systems landscape from becoming an unmaintainable nightmare.
Smaller is Better - Exploiting Microservice Architectures on AWS - Technical 201
Microservice oriented architectures have been implemented and deployed by many and are on the near-term agenda of many others. However, the distributed nature of microservices is a double edged sword, being the source of many of the benefits, but also the source of the pain and confusion that teams have endured. We will review best practices and recommended architectures for deploying microservices on AWS with a focus on how to exploit the benefits of microservices to decrease feature cycle times and costs while increasing reliability, scalability, and overall operational efficiency.
Speaker: Craig Dickson, Solutions Architect, Amazon Web Services
Featured Customer - MYOB
Airbnb, From Monolith to Microservices: How to Scale Your Architecture, Futur...
Hear from Melanie Cebula, Software Engineer at Airbnb, on how they utilize microservices to scale their architecture at FutureStack17 NYC.
See the video here: https://youtu.be/N1BWMW9NEQc
Be sure to subscribe and follow New Relic at:
https://twitter.com/NewRelic
https://www.facebook.com/NewRelic
https://www.youtube.com/NewRelicInc
Evolving Architecture and Organization - Lessons from Google and eBay
Keynote at DevOpsDays Cuba
Successful Internet companies are built on a foundation of excellent culture, efficient organization, and solid technology. As a company needs to scale, all of these parts of the foundation need to grow and scale with it. This session covers modern best practices at innovative companies in Silicon Valley for scaling culture, organization, and technology. Driven primarily by the presenter's experience ranging from small Valley startups to Google and eBay, it discusses:
* Organizing small, fast-moving engineering teams
* Building a scalable system out of smaller microservices
* Maintaining a culture of ownership and collaboration
* Developing effective engineering processes of continuous integration and continuous delivery
AWS Summit Auckland - Smaller is Better - Microservices on AWS
The document provides an overview of microservices including:
- Defining microservices and comparing them to SOA
- The benefits of a microservices architecture like improved agility, scalability, and innovation
- Common microservice patterns on AWS like serverless and container-based services
- How microservices can address business problems like long feature cycles and technical problems like lack of testability
- A customer story of how MYOB adopted microservices on AWS to support their online products
- Tips for evolving architectures including focusing on automation, organizational structure, and individual service design.
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig Dickson
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig DicksonAmazon Web Services Korea
This document provides an overview of microservices and how they can be implemented on AWS. It begins with defining microservices as independent services that work together to form an application. It then discusses how microservices address issues with monolithic architectures like tight coupling and lack of modularity. Various microservice patterns on AWS are presented, including using EC2 instances, ECS, Lambda, and serverless architectures. The document also explores how microservices can help address both business problems like long feature cycle times and technical problems like lack of testability. Overall, it aims to explain what microservices are, how they can be deployed on AWS, and the types of issues they can help organizations solve.Microservices easywaywrongway
Slides for the presentation on Microservices -- The Easy Way is the Wrong Way. The presentation is meant to show that to do microservices well a lot of other details are required.
Making sense of microservices, service mesh, and serverless
As companies move to become digital, we can get sidetracked and distracted by some of the changes in the technology landscape. Ideally we will be harnessing technology to solve the problems we have and leverage it to deliver software faster and safer. In this talk, I'll we'll take a look at some new technology trends in the open-source communities and when and how to use them.
Monoliths, Migrations, and Microservices
This talk describes several common challenges of software systems at scale:
* How to break up a monolithic application or a monolithic database into microservices.
* How to approach shared data, joins, and transactions in a microservices ecosystem
Concurrency at Scale: Evolution to Micro-Services
Most large-scale web companies have evolved their system architecture from a monolithic application and monolithic database to a set of loosely coupled micro-services. Using examples from Google, eBay, and KIXEYE, this talk outlines the pros and cons of these different stages of evolution, and makes practical suggestions about when and how other organizations should consider migrating to micro-services. It concludes with some more advanced implications of a micro-services architecture, including SLAs, cost-allocation, and vendor-customer relationships within the organization.
Serverless Toronto helps Startups
Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success!
In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA
Greach 2018: Surviving Microservices
The document discusses various topics related to surviving in a microservices environment. It begins by outlining some benefits of microservices such as reduced coupling, continuous delivery, and efficient scaling. It then covers infrastructure topics like managing logs, metrics, deployments, builds, and environments. Architecture topics discussed include overall design, technologies, testing approaches, communication methods, and data persistence. The document also addresses team communication and processes. It concludes by providing some miscellaneous advice for working with microservices.
More Related Content
Similar to Intro to Microservices
The "Why", "What" and "How" of Microservices
This document discusses microservices and alternatives to monolithic architectures. It begins by outlining the costs of software maintenance for monoliths and reasons why architectures need to change to adapt quickly. Alternatives like SOA are discussed, but microservices are presented as a way to break applications into fine-grained, independent services. However, the document cautions that simply breaking a monolith into smaller pieces does not automatically achieve decoupling, and improper use of microservices could result in even greater complexity. Autonomous services with explicit boundaries and asynchronous communication are emphasized as important characteristics to achieve decoupling.
Microservices music city code v2
- Microservices are an architectural style that structures an application as a collection of small, independent services that communicate with each other, often using RESTful API's. Each service focuses on doing a small job and is organized around business capabilities.
- The benefits of microservices include improved modularity, resilience, scalability, and autonomy for teams. Complexity is shifted outward so that services are easy to understand, enhance, test and deploy independently.
- Implementing microservices involves organizing code around business capabilities, following best practices like SOLID principles, domain-driven design, and contract-first development. It also requires automating delivery pipelines, monitoring, and abstracting service boundaries through techniques like API management and message
Surviving in a Microservices environment -abridged
Many presentations on Microservices offer a high-level view; rarely does one hear what it’s like to work in such an environment. Individual services are somewhat trivial to develop, but now you suddenly have countless others to track. You’ll become obsessed over how they communicate. You’ll have to start referring to the whole thing as “the Platform”. You will have to take on some considerable DevOps work and start learning about deployment pipelines, metrics, and logging.
Don’t panic. In this presentation we’ll discuss what we learned over the past four years by highlighting our mistakes. We’ll examine what a development lifecycle might look like for adding a new service, developing a feature, or fixing bugs. We’ll see how team communication is more important than one might realize. Most importantly, we’ll show how - while an individual service is simple - the infrastructure demands are now much more complicated: your organization will need to introduce and become increasingly dependent on various technologies, procedures, and tools - ranging from the ELK stack to Grafana to Kubernetes. Lastly, you’ll come away with the understanding that your resident SREs will become the most valued members of your team.
Microservices for Mortals by Bert Ertman at Codemotion Dubai
With popular poster children such as Netflix and Amazon, Microservices based architecture seems to be the killer approach to 21st century architectures. But are they only for Hollywood Coders pioneering on the bleeding edge of our profession? Or are they ready to be used for your projects and your customers? I will go over the benefits, but more so the pitfalls, of using a Microservices based architecture. What impact does it have on your organization, your applications, on dealing with scale and failures, and how do you prevent your landscape from becoming an unmaintainable nightmare.
Minimal Viable Architecture - Silicon Slopes 2020
This presentation introduces the idea of a "Minimal Viable Architecture". As a company and product evolves, its architecture should evolve as well. We talk about the different phases of a product -- from the idea phase, to the starting phase, scaling phase, and optimizing phase. For each phase, we discuss the goals and constraints on the business, and we suggest an appropriate software architecture to match. Throughout the presentation, we use examples from eBay, Google, StitchFix, and others.
Service Architectures at Scale
How do effective large-scale service ecosystems work? Keynote Presentation at Istanbul Tech Talks 2018
How to Design Services
* Systems of record
* Interface specification
* Interface backward / forward compatibility
Service Ecosystems
* Layered services
* "Standardization" through encouragement
* Vendor-customer relationships between teams
Operating and Deploying Services
* Data Migration
* Automated Pipelines
* Incremental Deployment
* Feature Flags
SACon 2019 - Surviving in a Microservices Environment
Many presentations on microservices offer a high-level view of the architecture; rarely do you hear what it’s like to work in such an environment. Stephen Pember shares his experience migrating from a monolith to microservices across several companies, highlighting the mistakes made along the way and offering advice.
Microserces Architecture
The document discusses microservice architecture, providing definitions and comparisons to monolithic and SOA architectures. It describes microservices as independently deployable services that work together to provide business capabilities. The benefits of microservices include evolutionary design, auto-scaling, and increased system resilience. Some challenges are also outlined, such as distributed logging and transaction spanning.
Microservices for Mortals
Microservices is the new popular kid on the block. Crowd pleaser at many conferences. With popular poster children such as Netflix and Amazon it seems to be the killer approach to 21st century architectures, right? But is this stuff only for Hollywood Coders pioneering on the bleeding edge of our profession? Or is this stuff ready to be used for your projects and your customers? This presentation is a warning. Microservices don't fix broken organizations and distributed computing is still hard. I will go over the benefits, but more so the pitfalls, of using a Microservices based architecture. What impact does it have on your applications, on dealing with scale and failures, and how do you prevent your systems landscape from becoming an unmaintainable nightmare.
Smaller is Better - Exploiting Microservice Architectures on AWS - Technical 201
Microservice oriented architectures have been implemented and deployed by many and are on the near-term agenda of many others. However, the distributed nature of microservices is a double edged sword, being the source of many of the benefits, but also the source of the pain and confusion that teams have endured. We will review best practices and recommended architectures for deploying microservices on AWS with a focus on how to exploit the benefits of microservices to decrease feature cycle times and costs while increasing reliability, scalability, and overall operational efficiency.
Speaker: Craig Dickson, Solutions Architect, Amazon Web Services
Featured Customer - MYOB
Airbnb, From Monolith to Microservices: How to Scale Your Architecture, Futur...
Hear from Melanie Cebula, Software Engineer at Airbnb, on how they utilize microservices to scale their architecture at FutureStack17 NYC.
See the video here: https://youtu.be/N1BWMW9NEQc
Be sure to subscribe and follow New Relic at:
https://twitter.com/NewRelic
https://www.facebook.com/NewRelic
https://www.youtube.com/NewRelicInc
Evolving Architecture and Organization - Lessons from Google and eBay
Keynote at DevOpsDays Cuba
Successful Internet companies are built on a foundation of excellent culture, efficient organization, and solid technology. As a company needs to scale, all of these parts of the foundation need to grow and scale with it. This session covers modern best practices at innovative companies in Silicon Valley for scaling culture, organization, and technology. Driven primarily by the presenter's experience ranging from small Valley startups to Google and eBay, it discusses:
* Organizing small, fast-moving engineering teams
* Building a scalable system out of smaller microservices
* Maintaining a culture of ownership and collaboration
* Developing effective engineering processes of continuous integration and continuous delivery
AWS Summit Auckland - Smaller is Better - Microservices on AWS
The document provides an overview of microservices including:
- Defining microservices and comparing them to SOA
- The benefits of a microservices architecture like improved agility, scalability, and innovation
- Common microservice patterns on AWS like serverless and container-based services
- How microservices can address business problems like long feature cycles and technical problems like lack of testability
- A customer story of how MYOB adopted microservices on AWS to support their online products
- Tips for evolving architectures including focusing on automation, organizational structure, and individual service design.
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig Dickson
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig DicksonAmazon Web Services Korea
This document provides an overview of microservices and how they can be implemented on AWS. It begins with defining microservices as independent services that work together to form an application. It then discusses how microservices address issues with monolithic architectures like tight coupling and lack of modularity. Various microservice patterns on AWS are presented, including using EC2 instances, ECS, Lambda, and serverless architectures. The document also explores how microservices can help address both business problems like long feature cycle times and technical problems like lack of testability. Overall, it aims to explain what microservices are, how they can be deployed on AWS, and the types of issues they can help organizations solve.Microservices easywaywrongway
Slides for the presentation on Microservices -- The Easy Way is the Wrong Way. The presentation is meant to show that to do microservices well a lot of other details are required.
Making sense of microservices, service mesh, and serverless
As companies move to become digital, we can get sidetracked and distracted by some of the changes in the technology landscape. Ideally we will be harnessing technology to solve the problems we have and leverage it to deliver software faster and safer. In this talk, I'll we'll take a look at some new technology trends in the open-source communities and when and how to use them.
Monoliths, Migrations, and Microservices
This talk describes several common challenges of software systems at scale:
* How to break up a monolithic application or a monolithic database into microservices.
* How to approach shared data, joins, and transactions in a microservices ecosystem
Concurrency at Scale: Evolution to Micro-Services
Most large-scale web companies have evolved their system architecture from a monolithic application and monolithic database to a set of loosely coupled micro-services. Using examples from Google, eBay, and KIXEYE, this talk outlines the pros and cons of these different stages of evolution, and makes practical suggestions about when and how other organizations should consider migrating to micro-services. It concludes with some more advanced implications of a micro-services architecture, including SLAs, cost-allocation, and vendor-customer relationships within the organization.
Serverless Toronto helps Startups
Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success!
In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA
Greach 2018: Surviving Microservices
The document discusses various topics related to surviving in a microservices environment. It begins by outlining some benefits of microservices such as reduced coupling, continuous delivery, and efficient scaling. It then covers infrastructure topics like managing logs, metrics, deployments, builds, and environments. Architecture topics discussed include overall design, technologies, testing approaches, communication methods, and data persistence. The document also addresses team communication and processes. It concludes by providing some miscellaneous advice for working with microservices.
Similar to Intro to Microservices (20)
Surviving in a Microservices environment -abridged
Surviving in a Microservices environment -abridged
Microservices for Mortals by Bert Ertman at Codemotion Dubai
Microservices for Mortals by Bert Ertman at Codemotion Dubai
SACon 2019 - Surviving in a Microservices Environment
SACon 2019 - Surviving in a Microservices Environment
Smaller is Better - Exploiting Microservice Architectures on AWS - Technical 201
Smaller is Better - Exploiting Microservice Architectures on AWS - Technical 201
Airbnb, From Monolith to Microservices: How to Scale Your Architecture, Futur...
Airbnb, From Monolith to Microservices: How to Scale Your Architecture, Futur...
Evolving Architecture and Organization - Lessons from Google and eBay
Evolving Architecture and Organization - Lessons from Google and eBay
AWS Summit Auckland - Smaller is Better - Microservices on AWS
AWS Summit Auckland - Smaller is Better - Microservices on AWS
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig Dickson
AWS Innovate: Smaller IS Better – Exploiting Microservices on AWS, Craig Dickson
Making sense of microservices, service mesh, and serverless
Making sense of microservices, service mesh, and serverless
Recently uploaded
Malibou Pitch Deck For Its €3M Seed Round
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
SMS API Integration in Saudi Arabia| Best SMS API Service
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
What next after learning python programming basics
What next after learning python programming basics
Mobile App Development Company In Noida | Drona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Modelling Up - DDDEurope 2024 - Amsterdam
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
How Can Hiring A Mobile App Development Company Help Your Business Grow?
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
原版定制美国纽约州立大学奥尔巴尼分校毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国纽约州立大学奥尔巴尼分校毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
GreenCode-A-VSCode-Plugin--Dario-Jurisic
Presentation about a VSCode plugin from Dario Jurisic at the GSD Community Stage meetup
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
Recently uploaded (20)
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
SMS API Integration in Saudi Arabia| Best SMS API Service
SMS API Integration in Saudi Arabia| Best SMS API Service
What next after learning python programming basics
What next after learning python programming basics
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
How Can Hiring A Mobile App Development Company Help Your Business Grow?
How Can Hiring A Mobile App Development Company Help Your Business Grow?
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Intro to Microservices
- 5. @reselbob Rule of the Road • I am not Mr. Know-It-All nor do I play him on TV • Run time questions requesting clarification are welcome • Big Picture questions and opinions are welcome at the end
- 6. @reselbob Moving to Microservices • What is a Microservice? • Real World Example • The Road to Microservices • Evolutions of Deployment Units • Evolution of SOA • Architectural Guidelines • Common Pitfalls • Avoiding the Common Pitfalls • Architecture • Demo on AWS • Next Steps • Questions and Answers
- 7. @reselbob What is a Microservice? A microservice is a piece of semantically distinct logic embedded in a fine grain deployment unit Small autonomous services that work together, modeled around a business domain — me — Sam Newman, ThoughtWorks
- 9. @reselbob The Road to Microservices You need to understand: • The Evolution of Deployment Units • The Evolution of Service Oriented Architecture
- 10. @reselbob Evolution of Deployment Units
- 12. @reselbob Separating the Data Server
- 13. @reselbob Separating the File System
- 17. @reselbob The Arrival of the Container
- 20. @reselbob A microservice is: • Discrete • Discoverable • Focused on Consumption • Responsible for its own data • Ephemeral • Immutable • Scalable
- 21. @reselbob Common Pitfalls • Synchronicity • State • Storage • Migrating Legacy Code
- 22. @reselbob Avoiding the Pitfalls Goal: Have multiple processes perform activities in a workflow
- 23. @reselbob Avoiding the Pitfalls Goal: Have multiple processes perform activities in a workflow function getWorkFlow(){ const workflow = []; const moesWork = getMoesWork(); workflow.push(moesWork); const larrysWork = getLarrysWork(); workflow.push(larrysWork); const curlysWork = getCurlysWork() workflow.push(curlysWork); return workflow; }
- 24. @reselbob Avoiding the Pitfalls Goal: Have multiple processes perform activities in a workflow function getWorkFlow(){ const workflow = []; return getMoesWork() .then(result => { workflow.push(result); return getLarrysWork(); }) .then(result =>{ workflow.push(result); return getCurlysWork() }) .then(result => { workflow.push(result); return workflow; }); }
- 27. @reselbob Next Steps • Understanding Discovery • Supporting State and Storage • Accommodating Legacy Code
- 28. @reselbob Questions and Answers Bob Reselman reselbob@gmail.com