In the last years the microservices architecture style has been gaining traction with some companies such as Netflix, Yelp, Gilt, PayPal. Many of that companies abandoned their previous monolithic architecture and moved to a microservices approach.
Does that mean that monolithic architectures are a thing of the past?
In this talk we will review some key microservices concepts (and misconceptions), search for the essence of microservices architectures and discuss about different approaches to implement them from the industry.
AWS re:Invent 2016: Automated Governance of Your AWS Resources (DEV302)Amazon Web Services
AWS CloudTrail, Amazon CloudWatch Events, AWS Identity & Access Management (IAM), Trusted Advisor, AWS Config Rules, other services? In this session, we will help you use existing and recently launched services to automate configuration governance so that security is embedded in the development process. We outline four easy steps (Control, Monitor, Fix, and Audit) and demonstrate how different services can be used to meet your governance needs. We will showcase real-life examples and you can take home a blog post with code examples and the full source code for scripts and tooling that AWS professional services have built using these services.
Pinterest is rolling out a phased platform migration from EC2-Classic to EC2-VPC. We used ClassicLink to link our EC2-Classic instances to VPCs, and we applied AWS best practices to configure VPC subnets and security groups. In this session, we share the lessons we learned along the way, and we also show you how to create a migration strategy and track migration costs.
Learn more about how Airtime works with microservices and ECS from start to finish: from developing against a local Vagrant environment, working with ECR and container images, utilizing CI/CD with CircleCI, to running a production workload on Amazon's ECS.
Revitalizing Walmart's Aging Architecture for Web ScaleKevin Webber
Learn how Walmart embraced the concepts of reactive programming, microservices, and domain-driven design to achieve results impossible only a decade ago.
Modernizing Applications with Microservices and DC/OS (Lightbend/Mesosphere c...Lightbend
**Featuring Aaron Williams, Head of Advocacy at Mesosphere, Inc. and Markus Eisele, Developer Advocate at Lightbend, Inc.**
The traditional architecture that enterprises run their businesses on has typically been delivered as monolithic applications running in a virtualized, on-premise infrastructure. Public and private cloud technologies have changed everything, but if the applications are not designed, or re-designed, appropriately, then it is impossible to take advantage of the advances in both distributed application services and hybrid infrastructure. Consequently, enterprise architects are looking to microservices-based architectures as a means to modernize their legacy applications.
This webinar with Lightbend and partner Mesosphere will introduce a new framework specifically designed to help developers modernize legacy Java EE applications into systems of microservices and then discuss exactly what is required to run these distributed systems at enterprise scale.
AWS re:Invent 2016: Automated Governance of Your AWS Resources (DEV302)Amazon Web Services
AWS CloudTrail, Amazon CloudWatch Events, AWS Identity & Access Management (IAM), Trusted Advisor, AWS Config Rules, other services? In this session, we will help you use existing and recently launched services to automate configuration governance so that security is embedded in the development process. We outline four easy steps (Control, Monitor, Fix, and Audit) and demonstrate how different services can be used to meet your governance needs. We will showcase real-life examples and you can take home a blog post with code examples and the full source code for scripts and tooling that AWS professional services have built using these services.
Pinterest is rolling out a phased platform migration from EC2-Classic to EC2-VPC. We used ClassicLink to link our EC2-Classic instances to VPCs, and we applied AWS best practices to configure VPC subnets and security groups. In this session, we share the lessons we learned along the way, and we also show you how to create a migration strategy and track migration costs.
Learn more about how Airtime works with microservices and ECS from start to finish: from developing against a local Vagrant environment, working with ECR and container images, utilizing CI/CD with CircleCI, to running a production workload on Amazon's ECS.
Revitalizing Walmart's Aging Architecture for Web ScaleKevin Webber
Learn how Walmart embraced the concepts of reactive programming, microservices, and domain-driven design to achieve results impossible only a decade ago.
Modernizing Applications with Microservices and DC/OS (Lightbend/Mesosphere c...Lightbend
**Featuring Aaron Williams, Head of Advocacy at Mesosphere, Inc. and Markus Eisele, Developer Advocate at Lightbend, Inc.**
The traditional architecture that enterprises run their businesses on has typically been delivered as monolithic applications running in a virtualized, on-premise infrastructure. Public and private cloud technologies have changed everything, but if the applications are not designed, or re-designed, appropriately, then it is impossible to take advantage of the advances in both distributed application services and hybrid infrastructure. Consequently, enterprise architects are looking to microservices-based architectures as a means to modernize their legacy applications.
This webinar with Lightbend and partner Mesosphere will introduce a new framework specifically designed to help developers modernize legacy Java EE applications into systems of microservices and then discuss exactly what is required to run these distributed systems at enterprise scale.
Beyond the brokers - Un tour de l'écosystème KafkaFlorent Ramiere
Apache Kafka ne se résume pas aux brokers, il y a tout un écosystème open-source qui gravite autour. Je vous propose ainsi de découvrir les principaux composants comme Kafka Streams, KSQL, Kafka Connect, Rest proxy, Schema Registry, MirrorMaker, etc.
AWS re:Invent 2016: VMware and AWS Together - VMware Cloud on AWS (ENT317)Amazon Web Services
VMware CloudTM on AWS brings VMware’s enterprise class Software-Defined Data Center software to Amazon’s public cloud, delivered as an on-demand, elastically scalable, cloud-based VMware sold, operated and supported service for any application and optimized for next-generation, elastic, bare metal AWS infrastructure. This solution enables customers to use a common set of software and tools to manage both their AWS-based and on-premises vSphere resources consistently. Further virtual machines in this environment have seamless access to the broad range of AWS services as well. This session will introduce this exciting new service and examine some of the use cases and benefits of the service. The session will also include a VMware Tech Preview that demonstrates standing up a complete SDDC cluster on AWS and various operations using standard tools like vCenter.
An overview of the Netflix Security Monkey Open Source tool. The presentation provides some background information, architectural overview, and screenshots showing the tool in action.
AWS re:Invent 2016: NEW LAUNCH! Lambda Everywhere (IOT309)Amazon Web Services
You can now execute Lambda’s almost anywhere – originating in the cloud, and on connected devices with AWS Greengrass. This advanced technical session explores Lambda Functions and what it means to use them across these diverse environments. We will treat the cloud as the ‘brain’, using local Lambda’s for local executions. This way devices can react instinctively, much like the autonomic nervous system, operating in the periphery and responsible for collecting and filtering information, implementing simple and time-sensitive local actions reflexively.
If you need to build highly performant, mission critical ,microservice-based system following DevOps best practices, you should definitely check Service Fabric!
Service Fabric is one of the most interesting services Azure offers today. It provide unique capabilities outperforming competitor products.
We are seeing global companies start to use Service Fabric for their mission critical solutions.
In this talk we explore the current state of Service Fabric and dive deeper to highlight best practices and design patterns.
We will cover the following topics:
• Service Fabric Core Concepts
• Cluster Planning and Management
• Stateless Services
• Stateful Services
• Actor Model
• Availability and reliability
• Scalability and perfromance
• Diganostics and Monitoring
• Containers
• Testing
• IoT
Live broadcast on https://www.youtube.com/watch?v=Zuxfhpab6xo
This session, gives an insider view of some the innovations that help make the AWS Cloud unique. He will show examples of AWS networking innovations from the interregional network backbone, through custom routers and networking rotocol stack, all the way down to individual servers. He will show examples from AWS server hardware, storage, and power distribution and then, up the stack, in high scale streaming data processing.
AWS re:Invent 2016: Securing Container-Based Applications (CON402)Amazon Web Services
Containers have had an incredibly large adoption rate since Docker was launched, especially from the developer community, as it provides an easy way to package, ship, and run applications. Securing your container-based application is now becoming a critical issue as applications move from development into production. In this session, you learn ways to implement storing secrets, distributing AWS privileges using IAM roles, protecting your container-based applications with vulnerability scans of container images, and incorporating automated checks into your continuous delivery workflow.
Architecting for the Cloud using NetflixOSS - Codemash WorkshopSudhir Tonse
Cloud development is inherently different than data center development. Understanding those differences, and architecting for them is critical to successful cloud solutions. In this workshop, we will both describe Netflix OSS platform components and show you how you can piece them together to build your own fault-tolerant REST services. These include: Hystrix, Ribbon, Eureka, and Archaius. In this hands-on lab, you will both learn the benefits of each of these services and use them in a sample application (in a test account). If you want to get things running in your own account, you may want to attend the afternoon session (Setting up your environment for the AWS cloud).
Netflix Open Source Meetup Season 4 Episode 3aspyker
In this episode, we will focus on security in the cloud at scale. We’ll have Netflix speakers discussing existing and upcoming security-related OSS releases, and we’ll also have external speakers from organizations that are using and contributing to Netflix security OSS.
First, Patrick Kelley from Netflix’s Security Operations team will speak about RepoMan, an upcoming OSS release designed to right-size AWS permissions. Then, Wes Miaw from Netflix’s Security Engineering team will discuss MSL (Message Security Layer).
We have two external speakers for this event - Chris Dorros from OpenDNS/Cisco will talk about his use of and contributions to Lemur, and Ryan Lane from Lyft will talk about their use of BLESS.
After the talks, we’ll have OSS authors at demo stations to answer questions and provide demos of Netflix security OSS, including Lemur, MSL, and Security Monkey.
Slides from the April 27th, 2016 Milwaukee Java Meetup held at DigitalMeasures in Milwaukee WI.
Example code and configuration at:
https://github.com/shall11672/mkej-config
https://github.com/shall11672/mkej-configServer
https://github.com/shall11672/mkej-eurekaService
https://github.com/shall11672/mkej-greetingService
https://github.com/shall11672/mkej-menuService
https://github.com/shall11672/mkej-apiGateway
https://github.com/shall11672/mkej-monitoringApplication
AWS re:Invent 2016: Service Integration Delivery and Automation Using Amazon ...Amazon Web Services
Through a combination of Amazon ECS and open source technologies, customers are able to build portable CI/CD pipelines on AWS. As container based deployments become more complex, they require additional rigging for integration. In this session, we show how popular Apache products like Kakfa, Storm, and Zookeeper are being deployed on top of Amazon ECS. We hear from HERE, a provider of mapping data, technologies, and services to the automotive, consumer, and enterprise sectors about an approach that leverages Consul from Hashicorp and Amazon ECS clusters for short-cycle deployments and tag-based environment promotion.
A presentation on the Netflix Cloud Architecture and NetflixOSS open source. For the All Things Open 2015 conference in Raleigh 2015/10/19. #ATO2015 #NetflixOSS
(SPOT205) 5 Lessons for Managing Massive IT Transformation ProjectsAmazon Web Services
Choice Hotels is undertaking a multiyear, $20 million project to recreate our core business engines on AWS. In trying to approach this complex undertaking, we determined that the project itself is a system too. You can apply principles of good architecture and design work in how you approach the project structure and management. Come to this talk by Choice Hotels’ CTO to learn five key lessons and 20 concrete takeaways that you can implement today to help your AWS projects succeed.
Microservices architectures are changing the way that organizations build their applications and infrastructure. Companies can now achieve new levels of scale and efficiency by disaggregating their large, monolithic applications into small, independent “micro services”, each of which perform different functions. In this session, we’ll introduce the concept of microservices, help you evaluate whether your organization is ready for microservices, and discuss methods for implementing these architectures.
AWS vs. Azure vs. Google vs. SoftLayer: Network, Storage and DBaaSRightScale
Most enterprises have a multi-cloud strategy, but choosing the right cloud for a workload can be challenging. In a previous deck we covered differences in block/object storage, pricing, and container services. In this deck we’ll drill down on archival storage, database-as-a-service (DBaaS), and networking options for the leading public clouds.
Have you heard that Machine Learning is the next big thing?
Are you a dummy in terms of Machine Learning, and think that is a topic for mathematicians with black-magic skills?
If your response to both questions is ‘Yes’, we are in the same position.
Still, thanks to the Web, Python and OpenSource libraries, we can overcome this situation and do some interesting stuff with Machine Learning.
Beyond the brokers - Un tour de l'écosystème KafkaFlorent Ramiere
Apache Kafka ne se résume pas aux brokers, il y a tout un écosystème open-source qui gravite autour. Je vous propose ainsi de découvrir les principaux composants comme Kafka Streams, KSQL, Kafka Connect, Rest proxy, Schema Registry, MirrorMaker, etc.
AWS re:Invent 2016: VMware and AWS Together - VMware Cloud on AWS (ENT317)Amazon Web Services
VMware CloudTM on AWS brings VMware’s enterprise class Software-Defined Data Center software to Amazon’s public cloud, delivered as an on-demand, elastically scalable, cloud-based VMware sold, operated and supported service for any application and optimized for next-generation, elastic, bare metal AWS infrastructure. This solution enables customers to use a common set of software and tools to manage both their AWS-based and on-premises vSphere resources consistently. Further virtual machines in this environment have seamless access to the broad range of AWS services as well. This session will introduce this exciting new service and examine some of the use cases and benefits of the service. The session will also include a VMware Tech Preview that demonstrates standing up a complete SDDC cluster on AWS and various operations using standard tools like vCenter.
An overview of the Netflix Security Monkey Open Source tool. The presentation provides some background information, architectural overview, and screenshots showing the tool in action.
AWS re:Invent 2016: NEW LAUNCH! Lambda Everywhere (IOT309)Amazon Web Services
You can now execute Lambda’s almost anywhere – originating in the cloud, and on connected devices with AWS Greengrass. This advanced technical session explores Lambda Functions and what it means to use them across these diverse environments. We will treat the cloud as the ‘brain’, using local Lambda’s for local executions. This way devices can react instinctively, much like the autonomic nervous system, operating in the periphery and responsible for collecting and filtering information, implementing simple and time-sensitive local actions reflexively.
If you need to build highly performant, mission critical ,microservice-based system following DevOps best practices, you should definitely check Service Fabric!
Service Fabric is one of the most interesting services Azure offers today. It provide unique capabilities outperforming competitor products.
We are seeing global companies start to use Service Fabric for their mission critical solutions.
In this talk we explore the current state of Service Fabric and dive deeper to highlight best practices and design patterns.
We will cover the following topics:
• Service Fabric Core Concepts
• Cluster Planning and Management
• Stateless Services
• Stateful Services
• Actor Model
• Availability and reliability
• Scalability and perfromance
• Diganostics and Monitoring
• Containers
• Testing
• IoT
Live broadcast on https://www.youtube.com/watch?v=Zuxfhpab6xo
This session, gives an insider view of some the innovations that help make the AWS Cloud unique. He will show examples of AWS networking innovations from the interregional network backbone, through custom routers and networking rotocol stack, all the way down to individual servers. He will show examples from AWS server hardware, storage, and power distribution and then, up the stack, in high scale streaming data processing.
AWS re:Invent 2016: Securing Container-Based Applications (CON402)Amazon Web Services
Containers have had an incredibly large adoption rate since Docker was launched, especially from the developer community, as it provides an easy way to package, ship, and run applications. Securing your container-based application is now becoming a critical issue as applications move from development into production. In this session, you learn ways to implement storing secrets, distributing AWS privileges using IAM roles, protecting your container-based applications with vulnerability scans of container images, and incorporating automated checks into your continuous delivery workflow.
Architecting for the Cloud using NetflixOSS - Codemash WorkshopSudhir Tonse
Cloud development is inherently different than data center development. Understanding those differences, and architecting for them is critical to successful cloud solutions. In this workshop, we will both describe Netflix OSS platform components and show you how you can piece them together to build your own fault-tolerant REST services. These include: Hystrix, Ribbon, Eureka, and Archaius. In this hands-on lab, you will both learn the benefits of each of these services and use them in a sample application (in a test account). If you want to get things running in your own account, you may want to attend the afternoon session (Setting up your environment for the AWS cloud).
Netflix Open Source Meetup Season 4 Episode 3aspyker
In this episode, we will focus on security in the cloud at scale. We’ll have Netflix speakers discussing existing and upcoming security-related OSS releases, and we’ll also have external speakers from organizations that are using and contributing to Netflix security OSS.
First, Patrick Kelley from Netflix’s Security Operations team will speak about RepoMan, an upcoming OSS release designed to right-size AWS permissions. Then, Wes Miaw from Netflix’s Security Engineering team will discuss MSL (Message Security Layer).
We have two external speakers for this event - Chris Dorros from OpenDNS/Cisco will talk about his use of and contributions to Lemur, and Ryan Lane from Lyft will talk about their use of BLESS.
After the talks, we’ll have OSS authors at demo stations to answer questions and provide demos of Netflix security OSS, including Lemur, MSL, and Security Monkey.
Slides from the April 27th, 2016 Milwaukee Java Meetup held at DigitalMeasures in Milwaukee WI.
Example code and configuration at:
https://github.com/shall11672/mkej-config
https://github.com/shall11672/mkej-configServer
https://github.com/shall11672/mkej-eurekaService
https://github.com/shall11672/mkej-greetingService
https://github.com/shall11672/mkej-menuService
https://github.com/shall11672/mkej-apiGateway
https://github.com/shall11672/mkej-monitoringApplication
AWS re:Invent 2016: Service Integration Delivery and Automation Using Amazon ...Amazon Web Services
Through a combination of Amazon ECS and open source technologies, customers are able to build portable CI/CD pipelines on AWS. As container based deployments become more complex, they require additional rigging for integration. In this session, we show how popular Apache products like Kakfa, Storm, and Zookeeper are being deployed on top of Amazon ECS. We hear from HERE, a provider of mapping data, technologies, and services to the automotive, consumer, and enterprise sectors about an approach that leverages Consul from Hashicorp and Amazon ECS clusters for short-cycle deployments and tag-based environment promotion.
A presentation on the Netflix Cloud Architecture and NetflixOSS open source. For the All Things Open 2015 conference in Raleigh 2015/10/19. #ATO2015 #NetflixOSS
(SPOT205) 5 Lessons for Managing Massive IT Transformation ProjectsAmazon Web Services
Choice Hotels is undertaking a multiyear, $20 million project to recreate our core business engines on AWS. In trying to approach this complex undertaking, we determined that the project itself is a system too. You can apply principles of good architecture and design work in how you approach the project structure and management. Come to this talk by Choice Hotels’ CTO to learn five key lessons and 20 concrete takeaways that you can implement today to help your AWS projects succeed.
Microservices architectures are changing the way that organizations build their applications and infrastructure. Companies can now achieve new levels of scale and efficiency by disaggregating their large, monolithic applications into small, independent “micro services”, each of which perform different functions. In this session, we’ll introduce the concept of microservices, help you evaluate whether your organization is ready for microservices, and discuss methods for implementing these architectures.
AWS vs. Azure vs. Google vs. SoftLayer: Network, Storage and DBaaSRightScale
Most enterprises have a multi-cloud strategy, but choosing the right cloud for a workload can be challenging. In a previous deck we covered differences in block/object storage, pricing, and container services. In this deck we’ll drill down on archival storage, database-as-a-service (DBaaS), and networking options for the leading public clouds.
Have you heard that Machine Learning is the next big thing?
Are you a dummy in terms of Machine Learning, and think that is a topic for mathematicians with black-magic skills?
If your response to both questions is ‘Yes’, we are in the same position.
Still, thanks to the Web, Python and OpenSource libraries, we can overcome this situation and do some interesting stuff with Machine Learning.
Presentation about the basics of Agile Methodologies and how they can be applied to Scientific Research. This presentation later evolved into the Agile Research method. June 2008
Comparing and contrasting monolithic systems to Lego pieces (microservices) at the 50,000 foot view. In this presentation we will compare and contrast monolithic systems to microservices. We will then take a look at some of the down sides to microservices. And then we will discuss some strategies for building microservices.
A alguns anos comecei a estudar para me tornar um Cientista de Dados. Ainda Não estou totalmente lá, mas essa palestra traz algumas coisas que aprendi e recursos para aprender ainda mais.
ES6 Metaprogramming presentation at MediterraneaJS on June 22th, 2015.
ES6 delivers some exciting metaprogramming capabilities with its new Proxies feature. Metaprogramming is powerful, but remember: "With great power comes great responsibility". In the talk we will shortly revisit Javascript metaprogramming and explain ES6 Proxies with code examples.
Anhand konkreter Projekte mit Schweizer Unternehmungen stellt das Datalab der Zürcher Hochschule für Angewandte Wissenschaften die Breite und Möglichkeiten für Data Science Anwendungen im Schweizer Markt dar. Praktische Erfahrung mit potentiellen Anwendungsfällen können interessierte Unternehmen dabei im Rahmen der „Big Data Roadshow“ der Firma Serwise sammeln.
How many of you have created an API? But how many created a good API?
A good API is like a good meal, makes developers extremely happy with a belly full - and for some companies who are API first having a simple, documented, reliable API is crucial.
When developers complain about your API it is maybe because you didn't design it well enough - intentions are surely important but design is king.
The Rapid API Prototyping talk, is all about bridging the gap between thinking and doing with focus on best practices, tooling and tricks to make developers LOVE your API at first sight.
Let's explore why you should have an API, how will it influence your business, why you should think about a monetisation seriously. There are a whole bunch of existing models that can help you find the right fit for your API depending on your roadmap.
Finally we take a look at the distribution of APIs to developers. Like any cake, you need to make sure it looks and tastes great to be able to sell it and be a leader!
Tools for designing and building great APIsKong Inc.
A review of tools that can be used to design APIs, understand how API design works and to mock infrastructure to test your assumptions.
We all know that a happy developer is a powerful ally.
The focus of this presentation is on the creation of APIs with the support of tools to achieve this. The goal is to create APIs that are simple for developers to understand and consume, powerful enough to be maintained by your business, in minutes rather than hours.
Versioning strategy for a complex internal API (Konstantin Yakushev)Nordic APIs
This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes.
When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API.
Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless.
This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product).
Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required.
This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API.
As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level.
In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years.
JAXLondon 2015 "DevOps and the Cloud: All Hail the (Developer) King"Daniel Bryant
Last year we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important but equally you must understand specific deployment technologies. How to exploit them and how they effect the design of applications. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same.
Presented at JAXLondon 2015 with Steve Poole
Slides for my keynote at incontrodevops.it, where I talked about distributed architectures, microservices, kubernetes and cloud native environments. All to get to the question: are microservices worth it?
It's easy to say... Microservices! Reality is we need to learn and apply concepts coming from many disciplines like SOA, EDA and DDD just to name a few! Mix them with some ALM and technical processes around Packaging and Deploying... and maybe then you get a true Microservices solution.
Slides for my architectural session at the event: Docker From Zero To Hero.
We talked about what kind of expertises are need in order to build a true Microservices Solution; you'll need to understand some of the fundamentals on which Microservices is built upon: SOA, EDA and DDD just to name a few, then you can move to the container world.
Original event link: https://www.eventbrite.it/e/biglietti-docker-from-zero-to-hero-83372825365#
Nowadays Microservices is perceived as the bulletproof software architecture choice. Monolithic applications are considered old fashioned. Isn’t there a sweet spot? What really makes us migrate from Monoliths to Microservices?
A presentation to explain the microservices architecture, the pro and the cons, with a view on how to migrate from a monolith to a SOA architecture. Also, we'll show the benefits of the microservices architecture also for the frontend side with the microfrontend architecture.
This presentation explores the Microservices architecture style. Although there is no precise definition of this architectural style (some argue Microservices is not an architectural style, just another term for SOA architectures), there is increasing agreement this approach is useful in implementing highly scalable, robust and configurable software systems.
We’ll attempt to clarify the topic from a purely architectural point of view dispelling some myths in the process.
This goal of this presentation is to present the rationale behind containers and how they can help you simplify your infrastructure and reduce cost and complexity. In this presentation I am showing the history and reasoning behind this technology which is used by world leading companies and how you can bring this technology and paradigm to bear to build distributed, fault tolerant, scalable solutions. This is only one of my many publications/solutions.
Similar to Elastically scalable architectures with microservices. The end of the monolith? (20)
There has been a lot of discussion during the last 50 years about the nature of programming: Is it an art like poetry? Is it craftsmanship like pottery? Is it an exact science like physics? Or a non exact science like medicine? Is it engineering like bridge building?
Whatever the nature of software development is: during this time, a lot of tools and techniques have appeared to make your lazy-developer life more difficult: Coding conventions, OOP, FP, SOLID, Design Patterns, Tests, TDD, UML, Use-cases, CASE tools, Refactoring, RUP, Agile, SCRUM, Continuous Integration, Code Complexity Metrics, Emergent Architecture, DevOps, SCM... and whatnot!
But, sometimes, being a lazy developer makes you do things that seemed counterintuitive, in order to pursue your main objective: WORK LESS.
MachineLearning for dummies with Python
Have you heard that Machine Learning is the next big thing?
Are you a dummy in terms of Machine Learning, and think that is a topic for mathematics with black-magic skills?
If your response to both questions is 'Yes', we are in the same position.
Still, thanks to the Web, Python and OpenSource libraries, we can overcome this situation and do some interesting stuff with Machine Learning.
Introduction to RabbitMQ, Amqp and some messaging patterns.
Easy to follow code examples step by step provided.
Sample code and escenarios can be found at: https://gist.github.com/javierarilos/9348168
At Telefonica PDI we are developing an internal messaging service to be used by our own products.
Sprayer is a low latency, reliable messaging system supporting delivery of messages to a single receiver, predefined group of receivers or specific list of receivers over different channels (SMS, HTTP, WebSockets, Email, Android, iOS and Firefox OS native push…). We are using Redis, MongoDB and RabbitMQ to implement Sprayer.
In this talk we will review Sprayer’s architecture. We will see for each of these technologies, why, where and for what they are used as well as some tips.
Talk done with Pablo Enfedaque ( @pablitoev56 ) at NoSQL Matters Barcelona 2013.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Globus Compute wth IRI Workflows - GlobusWorld 2024
Elastically scalable architectures with microservices. The end of the monolith?
1. The end of the monolith?
Elastically scalable architectures
with microservices.
2. Monolithic architecture
Feel the pain
intro
Netflix, PayPal, Twitter, Amazon…
What do they have in common?
Are monolithic architectures dead?
Distributed architecture with smaller services
3. about me
Javier Arias, senior software engineer at Telefonica.
Working during last year with a microservices in EyeOS, helping
to create an VDI (Virtual Desktop Infrastructure) platform.
@javier_arilos
http://about.me/javier.arilos
4. Back to the question
Objective:
To discuss about microservices
concepts & misconceptions
Are monolithic architectures dead?
5. A brief history of architectures
Mainframes,
Client/server (2 and then 3 tiers)
SOA
Microservices
6. Mainframe, Client/Server, SOA, Microservices…
They tried to solve architectural problems
And the history repeats
but… there is no silver bullet
18. microservices talking to microservices
API + lightweight communications
HTTP vs lightweight message bus
19. are your microservices good citizens?
stateless: key for scalability
failure ready: death or dependency failure
idempotent: repeated reqs yield same result
operations ready: logging, correlation...
24. monolith vs microservices: the essence
deploy many collaborating processes
vs
deploy single platform of components
25. simpler to deploy
more difficult to scale, specially deployment
monolith vs microservices: deploy
more complexity
scales better (software, teams and deployment)
microservices: many processes 2 deploy
monolith: one single ‘thing’ 2 deploy
26. prone to coupling: code, database
in-process calls
much easier to refactor and test
monolith vs microservices: distributed
computing
decoupled by deployment
distributed computing is hard:
failure-ready, many moving parts, testing
microservices: distributed computing
monolith: no distributed computing
27. consistency, simpler
operations are simpler
monolith vs microservices: platform
best tool for the job, more freedom, more
complexity
operations are more complex
microservices: many technoligies
monolith: constrained technologies
35. talk abstract
In the last years the microservices architecture style has been
gaining traction with some companies such as Netflix, Yelp,
Gilt, PayPal. Many of that companies abandoned their previous
monolithic architecture and moved to a microservices approach.
Does that mean that monolithic architectures are a thing of the
past?
In this talk we will review some key microservices concepts (and
misconceptions), search for the essence of microservices
architectures and discuss about different approaches to
implement them from the industry, including how we implemented
it in EyeOS.
Editor's Notes
What do Netflix, Yelp, Gilt, PayPal, Twitter, Amazon and others have in common?
they started with a monolithic architecture,
they are very successful companies and needed to scale: software, teams and do agile deployments
they started to feel pain by being blocked, by the architecture to scale and deploy.
they broke their monoliths into a distributed architecture with smaller services to release the pain
Are monoliths obsolete? Are monoliths a thing of the past?
Are monoliths obsolete? Are monoliths a thing of the past?
The objective of the talk is to show the main concepts and misconceptions about microservices versus monoliths.
MAINFRAMES
huge iron servers, server room, all applications in the same host, users were able to access the mainframe via "dumb terminals"
1950s mainframes begin to be available to big corporations and schools
in the 1970s, IBM released an operating system called VM that allowed admins on their System/370 mainframe systems to have multiple virtual systems, or "Virtual Machines" (VMs) on a single physical node
NASA shutted down its last mainframe in 2012, but probably, many of the your money transactions are still safely executed and stored in mainframes.
CLIENT/SERVER
as PCs improved their power, the idea to move processing capacity to the client started to catch on.
Client/server came in two flavors:
2 tiers, where local PCs run applications that connect to the shared database or even mainframe (mixing behaviour and database).
3 tiers, client, application server running the application, database.
SOA
SOA means so many different things to different people.
For some SOA is about exposing software through web services
For some SOA implies an architecture where applications disappear, core services that supply business functionality and data separated by UI aggregators that apply presentations that aggregate together the stuff that core services provide
For some SOA is about allowing systems to communicate over some form of standard structure (usually XML based) (CORBA with angle brackets)
For some SOA is all about using (mostly) asynchronous messaging to transfer documents between different systems. Essentially this is EAI
MICROSERVICES
Microservices could be seen as a subset of SOA where many of the ambiguity is removed.
CHEMISTRY. a substance that causes or accelerates a chemical reaction without itself being affected.
INTRO:
When talking about microservices architectures, we must talk not only about technology, but also about the complete software development cycle.
AGILE:
Agile software development and agile (or lean) product management, bring shorter release cycles, faster time-to-market, and more frequent small changes.
CONTAINERS:
Cloud and containers allow easiest application deployment, and programmable infrastructure (eg. elastically scale, single-use test environments…)
CONTINUOUS INTEGRATION:
Continuously merging code to main branch combined to automated tests (unit, integration, end to end, performance) in a pipeline makes that software at the end of the process may be deployed to production at any moment.
CHEMISTRY. a substance that causes or accelerates a chemical reaction without itself being affected.
INTRO:
When talking about microservices architectures, we must talk not only about technology, but also about the complete software development cycle.
AGILE:
Agile software development and agile (or lean) product management, bring shorter release cycles, faster time-to-market, and more frequent small changes.
CONTAINERS:
Cloud and containers allow easiest application deployment, and programmable infrastructure (eg. elastically scale, single-use test environments…)
CONTINUOUS INTEGRATION:
Continuously merging code to main branch combined to automated tests (unit, integration, end to end, performance) in a pipeline makes that software at the end of the process may be deployed to production at any moment.
CHEMISTRY. a substance that causes or accelerates a chemical reaction without itself being affected.
INTRO:
When talking about microservices architectures, we must talk not only about technology, but also about the complete software development cycle.
AGILE:
Agile software development and agile (or lean) product management, bring shorter release cycles, faster time-to-market, and more frequent small changes.
CONTAINERS:
Cloud and containers allow easiest application deployment, and programmable infrastructure (eg. elastically scale, single-use test environments…)
CONTINUOUS INTEGRATION:
Continuously merging code to main branch combined to automated tests (unit, integration, end to end, performance) in a pipeline makes that software at the end of the process may be deployed to production at any moment.
Continuous Integration is a software development practice where members of a team integrate their work frequently into the main branch of the Version Control System, usually each person integrates at least daily - leading to multiple integrations per day.
Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
Automatic build steps:
unit tests
code quality metrics
package (eg: create RPM, Docker container, Virtual Machine)
component, integration, end2end, performance tests
Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.
There is no single definition, and it depends on who you speak to.
My current favorite is the definition from Adrian Cockcroft, who is the architect behind Netflix migration to microservices architecture.
Loosely coupled service oriented architecture with bounded contexts.
(Adrian Cockcroft)
There is no single definition, and it depends on who you speak to.
My current favorite is the definition from Adrian Cockcroft, who is the architect behind Netflix migration to microservices architecture.
Loosely coupled service oriented architecture with bounded contexts.
(Adrian Cockcroft)
The main treat of loosely coupled services is the fact that they can be released and upgraded independently.
Shared databases was used frequently in the past to integrate different applications. It is one of the worst forms of coupling and forces to be very careful when making any change to the data or its schema. In microservices, each microservice cares about a little responsibility, and owns its data. No access to the domain managed by the microservice can be done if not done using APIs
Other sources of coupling can be shared libraries.
During the SOA fever, many middleware vendors proposed to add a coordination layer between applications. That layer would be responsible of many data transformations, routing, coordination of processes… and even some business logic. The result is that delivering new functionalities is coupled to many more pieces, making it much more difficult.
Each microservice run as a standalone process, this can lead to horizontal scalability, given the
All microservices talk exclusively using APIs, no database sharing.
This reduces coupling, but we still have services coupled by the API. When changing the API we can break everything or be forced to deploy different services at the same time. Semantic versioning helps reduce (not avoid) this problems.
In semantic versioning we use the different tokens in the version (eg: 2.3.23) to represent the impact of the changes in the API, from right to left: patch changes (bugfixing), minor changes (new functionalities), major changes (incompatible API changes).
Semantic versioning and microservices running as standalone processes help to design strategies for migrating APIs to major version releases (eg: having different versions running at the same time while migrating dependent services).
SIZE: Size is very important when talking about microservices. Microservices should have a size so that it is manea egarding size, there is some controversy here.
Some sources insist in defining microservices by the number of Lines of Code (LOC), but this is arbitrary and a non-sense.
The key point is HOW DO YOU DECIDE WHAT RESPONSIBILITIES BELONG TO A PARTICULAR SERVICE?
A service must specialize in do one thing and do it well. When it needs help, talks to other microservices by using their APIs.
Microservices should be organized by responsibility, domain or business capability.
Eric Evans in DDD (Domain Driven Design) talks about designing domain models as a very important part. When designing a system, the business model must reflect the reality: Customer, Bill, Product, Stock, Payment, … but in complex systems there are different realities. The same entity, eg: Customer has different properties in different contexts: eg departments of marketing, finance, logistics.
DDD defines BOUNDED CONTEXTS as a way to split big domain models in sets of entities that are significant in a given context (eg. finance department). Different contexts may have completely different models for common concepts with mechanisms to map between these polysemic concepts for integration.
SIZE AND CHATTY APIS: You must strike a balance here. If you fragment too much, cohesion of your application is too low, APIs are too chatty and you need too many interactions between microservices to do just one thing. If you make services too big, you risk to couple too much functionalities together.
PERSISTENCE AND LANGUAGE: one advantage of microservices is that each one is a standalone process that is independently developed, tested, released and operated. Each microservice uses its own data storage backend(s). Using different databases for different purposes is known as Polyglot Persistence.
This means that services can be developed using different programming languages and use different data storages. While this is stated as an advantage of microservices over monolithic architectures, we must be careful here. Finding a balance between finding the best tool for the job and introducing more complexity by using many different technologies.
I read an article some time ago that stated that when you develop an application you have a small number of tokens for investigation and problems. If you choose technologies that are immature or inestable you lose some of your tokens.
The nice thing about boring technologies is that the capabilities of these things are well understood. But more importantly, their failure modes are well understood.
When you choose a new technology, you are putting more stress in many aspects:operations, learning curve. You have to monitor the thing. You have to figure out unit tests, if it is a DB create and maintain a cluster, ...
Smart endpoints and dumb pipes: no intelligence should go into the communication mechanism (avoid ESB approach)
* Two main communication mechanisms: HTTP request response and lightweight message bus
* In a monolith components call each other via method invocation. A big issue migrating to microservices is converting to coarser grained APIs or end with chatty communications.
Other important characteristics of microservices:
STATELESS:
Being stateless mean that they do not keep any state inside. Stateless services only need the information in a request to handle it. Of course, for handling requests we will need to query databases or talk to other services, but no state is kept outside of the databases.
Statelessness implies that services can be started/stoppped at any moment without any risk, and that all requests can be load balanced between different service instances to improve scalability.
IDEMPOTENT:
repeated operations should yield the same result, or at least be prepared to receive repeated operations without failing.
FAILURE READY:
our microservices should be prepared to not lose operations in case of death or failure of a dependency (eg mongodb, redis, …)
EXAMPLE, if a request makes different two changes to a database and the process fails between first and second, our platform should ensure that we will receive the same request again later. A simple way of achieving this is using some message broker like RabbitMQ and manual Acknowledge of messages. If a process fails without acknowledge, it is requeued and delivered to another consumer.
When a brother process receives the request, repeats the first operation and it must not fail (Eg do upsert instead of insert, go on on duplicated...), then finish with the second operation and confirm the message in RabbitMQ
GOOD CITIZENS: there are many other small features that are very important in microservices architectures.
(Eg do upsert instead of insert, go on on duplicated...)
Let’s talk about other important aspects about microservices
With microservices, the execution environment is very dynamic,
microservices can be started or stopped at any time.
An important question arises: WHERE ARE MY SERVICES?
service discovery helps you have such a dynamic environment and be able to know the addresses of your services.
In EyeOS we are using consul.io
Discovering our services comes in two flavours:
DNS: our services know the name of the service, discovery service returns one of the available IPs
Database like Query: our services request the database about the service address, and then uses it.
It is very important to have service discovery linked to failure detection, so that discovery service returns only addresses of services that are running, and dynamically changes this list as services start or stop.
Now, you already have a successful project under heavy load from your uses… and you need to scale it.
Your microservices need to be stateless so that they can easily be started/stopped at any moment.
When you start a new service instance, it must start receiving requests. If you are using HTTP, you need your service discovery solution to be able to get requests to the new instance. If you are using a message broker, the new service will be a new competing consumer for a given queue/topic and automatically receives all messages.
With stateless services and load balancing, now, we can scale our services manually.
Since we have virtualization or containers, we can programatically add new nodes to our infrastructure, our microservices can be added and automatically start adding more processing capabilities to the platform.
In this moment, we would have the technical capabilities to dynamically scale. We need something that is able to start/stop microservices instances. That piece of code needs to know when to do it.
How we decide about scaling? Monitoring, but what? CPU? Requests received by a microservice? Request time, as seen by client? we can have many of them, we would need to aggregate data…
If you are using a message broker, there is a simple measure to check: QUEUE SIZE. Using it you can know when a microservice is receiving more requests that it is capable of processing.
As a summary, we can see some of the advantages of microservices
design: simple, loosely coupled (only talk through API)
physical: by physical here I mean features that are a consecuence of services released as a set of independent computer programs in different processes. appropiate tool for the job, deliver independently, enabler for continuous delivery.
This good parts are consequences of the microservices architecture.
As a summary, we can see some of the advantages of microservices
design: simple, loosely coupled (only talk through API)
physical: by physical here I mean features that are a consecuence of services released as a set of independent computer programs in different processes. appropiate tool for the job, deliver independently, enabler for continuous delivery.
This good parts are consequences of the microservices architecture.
As a summary, we can see some of the advantages of microservices
design: simple, loosely coupled (only talk through API)
physical: by physical here I mean features that are a consecuence of services released as a set of independent computer programs in different processes. appropiate tool for the job, deliver independently, enabler for continuous delivery.
This good parts are consequences of the microservices architecture.
As a summary, we can see some of the advantages of microservices
design: simple, loosely coupled (only talk through API)
physical: by physical here I mean features that are a consecuence of services released as a set of independent computer programs in different processes. appropiate tool for the job, deliver independently, enabler for continuous delivery.
This good parts are consequences of the microservices architecture.
What is really wrong with monoliths?
Bad Design and coupling. But you can do bad design also with microservices.
It is true that it is much more easier to couple (code or database) when everything is in the same process and there are no clear APIs between modules. But it is our fault as developers, not that monoliths are flawed.
On the other side, monoliths keeps many things much simpler (monitoring, CI, deployment, communications between modules, scaling, …). In simple projects, monoliths can help to deliver functionality faster… which is what it is expected from us.
In the first slide we were talking about Amazon, Netflix, Twitter… all started with monoliths and they went very very far before having o split them. Not that all of our projects will be as successful as that companies. For that reason, we should be very careful when deciding what architectural style to use.