Trasformare un'applicazione monolitica in microservices (versione #daje)
1 like9,625 views
The document discusses the challenges and strategies for disassembling monolithic applications into microservices, highlighting the benefits of microservices such as scalability and fault isolation while acknowledging the complexities introduced by distributed systems. It outlines a process for decomposition, emphasizes the importance of identifying business boundaries, and suggests using tools like RabbitMQ for inter-service communication. The speaker shares personal insights and opinions, encouraging a thoughtful approach to transitioning from a monolith to microservices.
1 of 86
Downloaded 10 times
![Sam Newman, author of Building Microservices
I remain convinced that it is much easier
to partition an existing [] system than
to do so up front
You have more to work with.](https://image.slidesharecdn.com/monolithdisassemble-codemotion-160322092925/85/Trasformare-un-applicazione-monolitica-in-microservices-versione-daje-40-320.jpg)
Ad
Recommended
Come ti smantello un'app monolitica in microservices
Come ti smantello un'app monolitica in microservicesmichele franzin
油
The document discusses the challenges and methodologies for disassembling a monolithic application into microservices. It outlines the characteristics of monolithic and microservice architectures, emphasizing the benefits of microservices such as improved fault isolation and independent deployment, while also addressing the complexities introduced by distributed systems. The author shares strategic steps for decomposition, highlights the importance of communication, and advocates for initially adopting a monolithic approach before transitioning to microservices.Microservices: cosa sono e quando non usarli
Microservices: cosa sono e quando non usarlimichele franzin
油
The document discusses microservices as a modern software architecture that allows for the independent deployment of small, decoupled services, facilitating modular application development. It contrasts microservices with monolithic architectures, highlighting benefits like simplicity, scalability, and technology diversity, while noting challenges such as increased complexity and communication overhead. The text advises a pragmatic approach, suggesting the consideration of monolithic designs first for smaller projects before transitioning to microservices.Secure Your Asses
Secure Your AssesAvivi Academy
油
The document discusses essential strategies for enhancing security in the modern digital landscape, focusing on password management, device protection, and data handling. Key recommendations include using secure passwords, employing password managers, and following the 3-2-1 backup rule. Additionally, it emphasizes the importance of being cautious in public spaces and recognizing social engineering tactics.Refactoring Into Microservices. Chicago Coders Conference 2017-06-26
Refactoring Into Microservices. Chicago Coders Conference 2017-06-26Derek Ashmore
油
Derek C. Ashmore discusses the challenges of refactoring monolithic applications into microservices, highlighting symptoms of monoliths such as long QA cycles and difficulties in maintenance. He advocates for iterative refactoring while maintaining the same technical stack, emphasizing that full rewrites can pose significant business risks and delays. Strategies presented include breaking down applications by functionality, addressing data store issues, and managing dependencies between services to facilitate a smoother transition to microservices.Transforming monolith systems to microservices
Transforming monolith systems to microservicesAlon Yair
油
The document discusses the transformation from monolithic software architecture to microservices, highlighting motivations, challenges, and strategies for successful implementation. Key benefits of microservices include shorter development cycles, improved scalability, and reduced failure points. Various techniques for transformation are outlined, such as using frameworks, gradual approaches, and optimizing traffic to enhance communication efficiency.Wie Monolithen f端r die Zukuft trimmen
Wie Monolithen f端r die Zukuft trimmenAnatole Tresch
油
The document discusses the challenges associated with monolithic software architectures and proposes microservices as a solution. It outlines the motivation for transitioning from monoliths to microservices, detailing the necessary infrastructure, design principles, and potential pitfalls. The presentation emphasizes the importance of careful planning, gradual implementation, and effective API design in successfully retrofitting existing systems.Refactoring Into Microservices 2016-11-06
Refactoring Into Microservices 2016-11-06Derek Ashmore
油
The document discusses the challenges of refactoring monolithic applications into microservices, highlighting symptoms of a monolith and the benefits of transitioning to microservices, such as increased speed to market and better management. It outlines various tactics for refactoring different types of monolithic applications, emphasizing the importance of iterative refactoring rather than complete rewrites. Key points include the need for proper automated testing, managing dependencies, and recognizing when refactoring is complete.Refactoring Into Microservices 2016-11-08
Refactoring Into Microservices 2016-11-08Derek Ashmore
油
Derek C. Ashmore gave a presentation on refactoring a monolithic application into microservices. He defined what a monolith is and the problems it can cause, such as being hard to change and having long test cycles. Ashmore discussed how breaking a monolith into smaller microservices can increase speed to market and lower business risk. He provided tactics for different types of monoliths, such as separating a user interface or factoring out independent services. Common challenges like handling shared code and reporting were also addressed.Beware the monolith
Beware the monolithDee Wilcox
油
The presentation by Dee Wilcox discusses the challenges and benefits of monolithic versus microservices architectures in enterprise-level development. It outlines the characteristics of monoliths, their benefits like simplicity and maintainability, and contrasts them with the advantages of microservices, which include better decoupling and ease of maintenance. Best practices for designing applications using microservices are provided, emphasizing the importance of APIs and security.Breaking down a monolith
Breaking down a monolithGeekNightHyderabad
油
This document discusses monolithic architectures and microservices architectures. It begins with an overview of what monoliths and microservices are. It then discusses some common issues with monoliths like lack of scalability and difficulty of changes. It provides examples of when monoliths may still be preferable and signs of a well-designed monolith. It then discusses microservices in more detail and their pros and cons. Two case studies are presented for gradually migrating parts of a monolith to microservices through either a phased or "big bang" approach. Distributed systems challenges are also covered. The document concludes by recommending starting with monoliths and refactoring later as needs dictate.Should i break it?
Should i break it?Gal Marder
油
The document discusses the transition from monolithic architecture to microservices, emphasizing that it's not simply about breaking up the monolith but involves changes in organizational structure, real separation of services, and cultivating a supporting culture. It highlights the importance of cross-functional teams, shared responsibility, and a robust platform for automation and monitoring. Additionally, it warns against common anti-patterns and stresses that successful microservices often evolve from existing monoliths rather than being built from scratch.Microservices and OSGi: Better together?
Microservices and OSGi: Better together?Graham Charters
油
The document discusses the relationship between microservices and OSGi, emphasizing the importance of modularity in software design. It highlights how microservices can improve application maintainability but also acknowledges the associated challenges and costs. OSGi is presented as a viable framework for creating modular monoliths, which can serve as a foundation for evolving to microservices.Pragmatic Microservices
Pragmatic MicroservicesRandy Shoup
油
The document outlines the evolution of software architecture from monolithic systems to microservices, detailing the advantages and challenges of each approach. It emphasizes the importance of organizational maturity, process maturity, and operational maturity in successfully implementing microservices. Additionally, it discusses rearchitecting strategies, including incremental migration and service anti-patterns, while noting situations where microservices may not be the appropriate solution.An introduction to Microservices
An introduction to MicroservicesCisco DevNet
油
This document provides an introduction to microservices architecture. It discusses why companies adopt the microservices style, how to design microservices, common patterns, and examples from Netflix.
The key points are:
1) Microservices architecture breaks applications into small, independent services that communicate over well-defined interfaces. This improves modularity, scalability, and allows independent deployments.
2) When designing microservices, services should be organized around business capabilities, have decentralized governance and data, and be designed to fail independently through patterns like circuit breakers.
3) Netflix is a leader in microservices and has open sourced many tools like Hystrix for latency handling and Eureka for service discovery thatOn microservices and monoliths
On microservices and monolithsDaniel Rolnick
油
The document discusses a talk on microservices and monoliths featuring speakers who are experts in software architecture and technology. Key topics include the advantages and disadvantages of microservices and monoliths, with microservices offering improved testability and scalability, while monoliths can reduce cognitive load. The session also involves interactive elements such as polling on software release practices and a game format to explore patterns of decoupling.Monoliths (and why you break 'em)
Monoliths (and why you break 'em)Nico Suria
油
Monoliths refer to applications that have become too large and unwieldy due to a lack of discernible architecture as the application has grown over time. Rails applications are particularly susceptible due to features that enable fast development but can lead to degeneration. Symptoms of a monolith include a lack of modularity, duplication, and coupling that make the application difficult to maintain, extend, deploy, and test. It is important to break a monolith into more logical modules to gain developer autonomy, enforced modularity, and easier debugging. This can be done by splitting the application into logical modules and grouping interdependent modules together in iterations until the structure is improved. There are implementation methods like using shared databases and libraries or web servicesAgile integration: Decomposing the monolith
Agile integration: Decomposing the monolith Judy Breedlove
油
This document discusses strategies for decomposing monolithic applications into microservices and ensuring resilience of the resulting microservices architecture. It covers decomposing monoliths using API-first and single responsibility principles. Managing the complex microservices architecture requires approaches for cross-cutting concerns like fault tolerance, traffic management, policy enforcement, distributed tracing, and infrastructure concerns like circuit breaking. A service mesh like Istio deployed as sidecars can provide a communications control plane for traffic management, policy enforcement, and distributed tracing between microservices.Lowering the risk of monolith to microservices
Lowering the risk of monolith to microservicesChristian Posta
油
This document summarizes one organization's journey from a monolithic application architecture to a microservices architecture. It describes some of the pains of maintaining a monolithic application. It then discusses strategies for breaking the monolith into independently deployable microservices at low risk, including identifying module boundaries, deploying and releasing services independently, virtualizing data integration, and using traffic mirroring. The goal is to increase development velocity while lowering risk.Breaking Down the Monolith at Uberflip
Breaking Down the Monolith at UberflipYoav Schwartz
油
The document uses the analogy of Bob building a house to explain the concept of breaking down a monolithic architecture into smaller, interconnected services. It illustrates how a growing application can become overly complex if not designed with scalability in mind. By transitioning to a system of smaller services, developers can improve code separation, performance, and maintenance. Microservices for Mortals by Bert Ertman at Codemotion Dubai
Microservices for Mortals by Bert Ertman at Codemotion DubaiCodemotion Dubai
油
The document discusses the evolution and challenges of microservices architecture, contrasting it with traditional monolithic and SOA approaches. It emphasizes that while microservices can enhance business agility and flexibility, they also introduce complexities such as data management, service communication, and the need for organizational alignment. The author advises caution against blindly following trends and encourages thoughtful implementation and understanding of the principles behind microservices.Introduction to microservices
Introduction to microservicesAnil Allewar
油
The document provides an introduction to microservices, detailing their characteristics, advantages, and the methodology of 12-factor apps essential for building scalable SaaS applications. It discusses the transition from monolithic architecture to microservices, emphasizing componentization, decentralized governance, and the importance of a well-designed system. Additionally, it highlights potential challenges in microservices adoption and lists various frameworks suitable for implementation.Nir Doboviski: In Space No One Can Hear Microservices Scream a Microservice...
Nir Doboviski: In Space No One Can Hear Microservices Scream a Microservice...CodeValue
油
The document discusses the complexities and advantages of microservices in the context of software architecture, particularly in satellite ground station systems. It emphasizes that while microservices offer benefits like scalability and fault tolerance, they can also lead to increased complexity and management overhead, especially for smaller teams. Recommendations for implementation vary based on the size of the development team, suggesting monoliths for smaller teams and microservices for larger organizations.The 6 Rules for Modernizing Your Legacy Java Monolith with Microservices
The 6 Rules for Modernizing Your Legacy Java Monolith with MicroservicesLightbend
油
The document outlines six key rules for modernizing a legacy Java monolith into microservices, highlighting the benefits of microservices such as scalability, resilience, and independent deployment. It discusses principles of domain-driven design, async messaging, and transaction management in distributed systems, as well as tools like Play and Akka for implementation. Additionally, it offers guidance on API management, dependency management, and event sourcing, concluding with a promotional note about Lightbend's services for transitioning to microservices."The working architecture of NodeJs applications" Viktor Turskyi
"The working architecture of NodeJs applications" Viktor TurskyiJulia Cherniak
油
Viktor Turskyi discusses a refined approach for building web applications using a unified architecture applicable across Node.js, PHP, and Perl, advocating for a monolith over microservices due to lower complexity and costs. He emphasizes the importance of clear MVC structuring, service layers, and robust validation to avoid issues such as anemic domain models. The talk covers practical examples, rules for implementation, and the benefits of a web framework-agnostic methodology that eases technology transitions and fosters knowledge sharing.L11 Service Design and REST
L11 Service Design and RESTlafur Andri Ragnarsson
油
This document provides an overview of service design and REST architectures. It discusses key concepts like microservices, APIs, service boundaries, and Conway's Law. It explains that services should be organized around business capabilities and have well-defined interfaces. REST architectural styles are also covered, including the Richardson Maturity Model levels and best practices like resources, uniform interfaces, and HATEOAS. Overall, the document is a useful introduction to designing and modeling service-oriented systems using REST principles.Monoliths and Microservices
Monoliths and Microservices Bozhidar Bozhanov
油
The document discusses the differences between monolithic and microservices architectures, highlighting the advantages and disadvantages of each approach. It emphasizes that while microservices offer benefits such as modularity and independent deployment, they also come with downsides like network overhead and complexity. Ultimately, the recommendation is to consider using a monolith unless dealing with overly complex systems, promoting good modularity within that framework.Microservice Architecture
Microservice ArchitectureDhaval Shah
油
The document discusses moving from a monolithic architecture to microservices. A monolithic application can be difficult to maintain, upgrade, and scale as it grows in size. Microservices break an application into smaller, independent services that can be developed and deployed independently. This improves maintainability, scalability, and allows incremental upgrades. However, microservices come with additional complexity from managing more distributed components and potential performance impacts from additional network calls. The document provides design considerations and best practices for implementing microservices, such as domain-driven design and event-driven asynchronous communication between services.Designing Scalable and Secure Microservices by Embracing DevOps-as-a-Service ...
Designing Scalable and Secure Microservices by Embracing DevOps-as-a-Service ...Demetris Trihinas
油
This document provides an overview of a tutorial on designing scalable and secure microservices. It discusses the evolution of software architectures from monolithic applications to microservices and the benefits of microservices for scalability, innovation, and continuous delivery. It also covers challenges such as coordination and deployment complexities that microservices aim to address through practices like containerization, automation, and decentralized governance.Unleashing git power
Unleashing git powermichele franzin
油
The document discusses best practices for using Git, a distributed version control system, with a focus on commands such as 'git stash', 'git rebase', and conflict resolution. It includes practical tips for managing repositories and emphasizes the importance of a clear commit history. Additionally, the content promotes the idea of developer and colleague happiness while handling code and version control.1 anno di sviluppo prodotto con un team distribuito
1 anno di sviluppo prodotto con un team distribuitomichele franzin
油
The document reflects on a year of product development with a distributed team, highlighting lessons learned about remote work and teamwork. It emphasizes the importance of communication, trust, and empathy over metrics or tools, addressing challenges like communication difficulties and time management. The overall message advocates for a positive work environment and prioritizing human interactions.More Related Content
Similar to Trasformare un'applicazione monolitica in microservices (versione #daje) (20)
Beware the monolith
Beware the monolithDee Wilcox
油
The presentation by Dee Wilcox discusses the challenges and benefits of monolithic versus microservices architectures in enterprise-level development. It outlines the characteristics of monoliths, their benefits like simplicity and maintainability, and contrasts them with the advantages of microservices, which include better decoupling and ease of maintenance. Best practices for designing applications using microservices are provided, emphasizing the importance of APIs and security.Breaking down a monolith
Breaking down a monolithGeekNightHyderabad
油
This document discusses monolithic architectures and microservices architectures. It begins with an overview of what monoliths and microservices are. It then discusses some common issues with monoliths like lack of scalability and difficulty of changes. It provides examples of when monoliths may still be preferable and signs of a well-designed monolith. It then discusses microservices in more detail and their pros and cons. Two case studies are presented for gradually migrating parts of a monolith to microservices through either a phased or "big bang" approach. Distributed systems challenges are also covered. The document concludes by recommending starting with monoliths and refactoring later as needs dictate.Should i break it?
Should i break it?Gal Marder
油
The document discusses the transition from monolithic architecture to microservices, emphasizing that it's not simply about breaking up the monolith but involves changes in organizational structure, real separation of services, and cultivating a supporting culture. It highlights the importance of cross-functional teams, shared responsibility, and a robust platform for automation and monitoring. Additionally, it warns against common anti-patterns and stresses that successful microservices often evolve from existing monoliths rather than being built from scratch.Microservices and OSGi: Better together?
Microservices and OSGi: Better together?Graham Charters
油
The document discusses the relationship between microservices and OSGi, emphasizing the importance of modularity in software design. It highlights how microservices can improve application maintainability but also acknowledges the associated challenges and costs. OSGi is presented as a viable framework for creating modular monoliths, which can serve as a foundation for evolving to microservices.Pragmatic Microservices
Pragmatic MicroservicesRandy Shoup
油
The document outlines the evolution of software architecture from monolithic systems to microservices, detailing the advantages and challenges of each approach. It emphasizes the importance of organizational maturity, process maturity, and operational maturity in successfully implementing microservices. Additionally, it discusses rearchitecting strategies, including incremental migration and service anti-patterns, while noting situations where microservices may not be the appropriate solution.An introduction to Microservices
An introduction to MicroservicesCisco DevNet
油
This document provides an introduction to microservices architecture. It discusses why companies adopt the microservices style, how to design microservices, common patterns, and examples from Netflix.
The key points are:
1) Microservices architecture breaks applications into small, independent services that communicate over well-defined interfaces. This improves modularity, scalability, and allows independent deployments.
2) When designing microservices, services should be organized around business capabilities, have decentralized governance and data, and be designed to fail independently through patterns like circuit breakers.
3) Netflix is a leader in microservices and has open sourced many tools like Hystrix for latency handling and Eureka for service discovery thatOn microservices and monoliths
On microservices and monolithsDaniel Rolnick
油
The document discusses a talk on microservices and monoliths featuring speakers who are experts in software architecture and technology. Key topics include the advantages and disadvantages of microservices and monoliths, with microservices offering improved testability and scalability, while monoliths can reduce cognitive load. The session also involves interactive elements such as polling on software release practices and a game format to explore patterns of decoupling.Monoliths (and why you break 'em)
Monoliths (and why you break 'em)Nico Suria
油
Monoliths refer to applications that have become too large and unwieldy due to a lack of discernible architecture as the application has grown over time. Rails applications are particularly susceptible due to features that enable fast development but can lead to degeneration. Symptoms of a monolith include a lack of modularity, duplication, and coupling that make the application difficult to maintain, extend, deploy, and test. It is important to break a monolith into more logical modules to gain developer autonomy, enforced modularity, and easier debugging. This can be done by splitting the application into logical modules and grouping interdependent modules together in iterations until the structure is improved. There are implementation methods like using shared databases and libraries or web servicesAgile integration: Decomposing the monolith
Agile integration: Decomposing the monolith Judy Breedlove
油
This document discusses strategies for decomposing monolithic applications into microservices and ensuring resilience of the resulting microservices architecture. It covers decomposing monoliths using API-first and single responsibility principles. Managing the complex microservices architecture requires approaches for cross-cutting concerns like fault tolerance, traffic management, policy enforcement, distributed tracing, and infrastructure concerns like circuit breaking. A service mesh like Istio deployed as sidecars can provide a communications control plane for traffic management, policy enforcement, and distributed tracing between microservices.Lowering the risk of monolith to microservices
Lowering the risk of monolith to microservicesChristian Posta
油
This document summarizes one organization's journey from a monolithic application architecture to a microservices architecture. It describes some of the pains of maintaining a monolithic application. It then discusses strategies for breaking the monolith into independently deployable microservices at low risk, including identifying module boundaries, deploying and releasing services independently, virtualizing data integration, and using traffic mirroring. The goal is to increase development velocity while lowering risk.Breaking Down the Monolith at Uberflip
Breaking Down the Monolith at UberflipYoav Schwartz
油
The document uses the analogy of Bob building a house to explain the concept of breaking down a monolithic architecture into smaller, interconnected services. It illustrates how a growing application can become overly complex if not designed with scalability in mind. By transitioning to a system of smaller services, developers can improve code separation, performance, and maintenance. Microservices for Mortals by Bert Ertman at Codemotion Dubai
Microservices for Mortals by Bert Ertman at Codemotion DubaiCodemotion Dubai
油
The document discusses the evolution and challenges of microservices architecture, contrasting it with traditional monolithic and SOA approaches. It emphasizes that while microservices can enhance business agility and flexibility, they also introduce complexities such as data management, service communication, and the need for organizational alignment. The author advises caution against blindly following trends and encourages thoughtful implementation and understanding of the principles behind microservices.Introduction to microservices
Introduction to microservicesAnil Allewar
油
The document provides an introduction to microservices, detailing their characteristics, advantages, and the methodology of 12-factor apps essential for building scalable SaaS applications. It discusses the transition from monolithic architecture to microservices, emphasizing componentization, decentralized governance, and the importance of a well-designed system. Additionally, it highlights potential challenges in microservices adoption and lists various frameworks suitable for implementation.Nir Doboviski: In Space No One Can Hear Microservices Scream a Microservice...
Nir Doboviski: In Space No One Can Hear Microservices Scream a Microservice...CodeValue
油
The document discusses the complexities and advantages of microservices in the context of software architecture, particularly in satellite ground station systems. It emphasizes that while microservices offer benefits like scalability and fault tolerance, they can also lead to increased complexity and management overhead, especially for smaller teams. Recommendations for implementation vary based on the size of the development team, suggesting monoliths for smaller teams and microservices for larger organizations.The 6 Rules for Modernizing Your Legacy Java Monolith with Microservices
The 6 Rules for Modernizing Your Legacy Java Monolith with MicroservicesLightbend
油
The document outlines six key rules for modernizing a legacy Java monolith into microservices, highlighting the benefits of microservices such as scalability, resilience, and independent deployment. It discusses principles of domain-driven design, async messaging, and transaction management in distributed systems, as well as tools like Play and Akka for implementation. Additionally, it offers guidance on API management, dependency management, and event sourcing, concluding with a promotional note about Lightbend's services for transitioning to microservices."The working architecture of NodeJs applications" Viktor Turskyi
"The working architecture of NodeJs applications" Viktor TurskyiJulia Cherniak
油
Viktor Turskyi discusses a refined approach for building web applications using a unified architecture applicable across Node.js, PHP, and Perl, advocating for a monolith over microservices due to lower complexity and costs. He emphasizes the importance of clear MVC structuring, service layers, and robust validation to avoid issues such as anemic domain models. The talk covers practical examples, rules for implementation, and the benefits of a web framework-agnostic methodology that eases technology transitions and fosters knowledge sharing.L11 Service Design and REST
L11 Service Design and RESTlafur Andri Ragnarsson
油
This document provides an overview of service design and REST architectures. It discusses key concepts like microservices, APIs, service boundaries, and Conway's Law. It explains that services should be organized around business capabilities and have well-defined interfaces. REST architectural styles are also covered, including the Richardson Maturity Model levels and best practices like resources, uniform interfaces, and HATEOAS. Overall, the document is a useful introduction to designing and modeling service-oriented systems using REST principles.Monoliths and Microservices
Monoliths and Microservices Bozhidar Bozhanov
油
The document discusses the differences between monolithic and microservices architectures, highlighting the advantages and disadvantages of each approach. It emphasizes that while microservices offer benefits such as modularity and independent deployment, they also come with downsides like network overhead and complexity. Ultimately, the recommendation is to consider using a monolith unless dealing with overly complex systems, promoting good modularity within that framework.Microservice Architecture
Microservice ArchitectureDhaval Shah
油
The document discusses moving from a monolithic architecture to microservices. A monolithic application can be difficult to maintain, upgrade, and scale as it grows in size. Microservices break an application into smaller, independent services that can be developed and deployed independently. This improves maintainability, scalability, and allows incremental upgrades. However, microservices come with additional complexity from managing more distributed components and potential performance impacts from additional network calls. The document provides design considerations and best practices for implementing microservices, such as domain-driven design and event-driven asynchronous communication between services.Designing Scalable and Secure Microservices by Embracing DevOps-as-a-Service ...
Designing Scalable and Secure Microservices by Embracing DevOps-as-a-Service ...Demetris Trihinas
油
This document provides an overview of a tutorial on designing scalable and secure microservices. It discusses the evolution of software architectures from monolithic applications to microservices and the benefits of microservices for scalability, innovation, and continuous delivery. It also covers challenges such as coordination and deployment complexities that microservices aim to address through practices like containerization, automation, and decentralized governance.More from michele franzin (6)
Unleashing git power
Unleashing git powermichele franzin
油
The document discusses best practices for using Git, a distributed version control system, with a focus on commands such as 'git stash', 'git rebase', and conflict resolution. It includes practical tips for managing repositories and emphasizes the importance of a clear commit history. Additionally, the content promotes the idea of developer and colleague happiness while handling code and version control.1 anno di sviluppo prodotto con un team distribuito
1 anno di sviluppo prodotto con un team distribuitomichele franzin
油
The document reflects on a year of product development with a distributed team, highlighting lessons learned about remote work and teamwork. It emphasizes the importance of communication, trust, and empathy over metrics or tools, addressing challenges like communication difficulties and time management. The overall message advocates for a positive work environment and prioritizing human interactions....hai detto CQRS a chi ?!?!?!
...hai detto CQRS a chi ?!?!?! michele franzin
油
CQRS, or Command Query Responsibility Segregation, is an architectural pattern that separates read and write operations into distinct subsystems to enhance scalability and flexibility. It is important to understand its myths and limitations, such as potential complexity and the need for eventual consistency. The document discusses the benefits, considerations for use, and suggests alternatives like event sourcing.Ruby 20th birthday
Ruby 20th birthdaymichele franzin
油
The document celebrates the 20th birthday of Ruby, highlighting its design for programmer productivity and its features such as reflection, garbage collection, and strong dynamic typing. It discusses various implementations, versions, and programming concepts like closures, metaprogramming, and lazy enumerables. Additionally, it touches on Ruby's compatibility with previous versions and provides resources for further learning.Magie di git
Magie di gitmichele franzin
油
- Git is an open source version control system designed to handle large projects efficiently with non-linear and distributed development.
- It uses cryptographic authentication and supports HTTP, FTP, SSH, rsync or its own Git protocol.
- Basic Git workflow involves making changes, staging them with git add, and committing with descriptive messages. History can be explored with commands like git log and git show.from(0).to('rubygems.org')
from(0).to('rubygems.org')michele franzin
油
This document discusses RubyGems and the process for creating and publishing a Ruby gem. It explains that a gem is a packaged Ruby application or library with a name and version. It then provides steps for building a gem using different tools like Bundler, Jeweler, and Hoe+Echoe. It also outlines the process of building, installing and publishing a gem to RubyGems.org including using a Rubygems API key in the credentials file.Ad
Recently uploaded (20)
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptx
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptxMaharshi Mallela
油
Movie recommendation system is a software application or algorithm designed to suggest movies to users based on their preferences, viewing history, or other relevant factors. The primary goal of such a system is to enhance user experience by providing personalized and relevant movie suggestions.HYBRIDIZATION OF ALKANES AND ALKENES ...
HYBRIDIZATION OF ALKANES AND ALKENES ...karishmaduhijod1
油
Hybridization happens when atomic orbitals mix to form a new atomic orbital. Enable Your Cloud Journey With Microsoft Trusted Partner | IFI Tech
Enable Your Cloud Journey With Microsoft Trusted Partner | IFI TechIFI Techsolutions
油
Start your cloud journey with IFI TechMicrosofts trusted partner delivering secure, scalable Azure solutions tailored for your business.
Key Challenges in Troubleshooting Customer On-Premise Applications
Key Challenges in Troubleshooting Customer On-Premise ApplicationsTier1 app
油
When applications are deployed in customer-managed environments, resolving performance issues becomes a hidden battle. Limited access to logs, delayed responses, and vague problem descriptions make root cause analysis incredibly challenging.
In this presentation, we walk through:
The six most common hurdles faced in on-prem troubleshooting
A practical 360属 artifact collection strategy using the open-source yc-360 script
Real-world case studies covering transaction timeouts, CPU spikes, and intermittent HTTP 502 errors
Benefits of structured data capture in reducing investigation time and improving communication with customers
Whether you're supporting enterprise clients or building tools for distributed environments, this deck offers a practical roadmap to make on-prem issue resolution faster and less frustrating.arctitecture application system design os dsa
arctitecture application system design os dsaza241967
油
wow amazing see and enjoy for this the best pdf slideshow you could see random shit is what i do best Why Edge Computing Matters in Mobile Application Tech.pdf
Why Edge Computing Matters in Mobile Application Tech.pdfIMG Global Infotech
油
This PDF explores the critical role of edge computing in modern mobile application technology. Learn how edge enhances app speed, reduces latency, improves data privacy, and supports real-time performance. Ideal for developers, tech strategists, and mobile innovators looking to stay ahead in the evolving mobile ecosystem.Canva Pro Crack Free Download 2025-FREE LATEST
Canva Pro Crack Free Download 2025-FREE LATESTgrete1122g
油
艶COPY & PASTE LINK >> https://click4pc.com/after-verification-click-go-to-download-page/
Canva Pro PC Crack is a practical design app to create beautiful montages and compositions with a lot of resources on the platform.Decipher SEO Solutions for your startup needs.
Decipher SEO Solutions for your startup needs.mathai2
油
A solution deck that gives you an idea of how you can use Decipher SEO to target keywords, build authority and generate high ranking content.
With features like images to product you can create a E-commerce pipeline that is optimized to help your store rank.
With integrations with shopify, woocommerce and wordpress theres a seamless way get your content to your website or storefront.
View more at decipherseo.comAdvance Doctor Appointment Booking App With Online Payment
Advance Doctor Appointment Booking App With Online PaymentAxisTechnolabs
油
/slideshow/advance-doctor-appointment-booking-app-with-online-payment/280654375Azure AI Foundry: The AI app and agent factory
Azure AI Foundry: The AI app and agent factoryMaxim Salnikov
油
Discover how Azure AI Foundry is transforming the way organizations innovate and operate. This session explores the pivotal role of AI in reshaping business processes, enhancing employee experiences, and redefining customer engagement. Attendees will gain insights into the strategic value of AI investments, including the measurable returns and the growing momentum behind generative AI experimentation.
The talk introduces the emerging paradigm of agentic AI - intelligent agents that are revolutionizing how we build, manage, and interact with software. Through real-world examples, the session demonstrates how Azure AI Foundry empowers teams to design, customize, and scale AI applications and agents, unlocking new levels of efficiency and creativity across industries.Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025
Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025BradBedford3
油
Join us for an exciting introductory session on, Foundations of Marketo Engage: Programs, Campaigns & Beyond. Ideal for new and early-stage users looking to build confidence and capability in Marketo Engage.
Our speakers for this session will be:
AJ Navarro
Marketing Operations Manager - Sprout Social
Bobby Coppola
Marketing Manager - Blue Yonder
This event will guide you through the essential steps to build strong, scalable Programs, Channels, Tags, Smart Campaigns, and Reporting Basics in Marketo Engage.
Attendees will gain practical knowledge on how to structure and launch marketing initiatives, leverage templates for efficiency, and implement best practices for campaign execution and measurement. You'll leave with actionable insights you can immediately apply to your own Marketo instance to improve organization, automation, and reporting. Marketo Engage.
Learn how to create impactful programs and understand the best practices for seamless campaign management and effective reporting.
Dont miss out on this opportunity to gain hands-on guidance from experienced practitioners and to connect with peers who are also new to the platform. Secure your spot today and start building your path to becoming a Marketo pro!
Please feel free to invite colleagues who you think would also benefit from this session.IDM Crack with Internet Download Manager 6.42 Build 41 [Latest 2025]
IDM Crack with Internet Download Manager 6.42 Build 41 [Latest 2025]pcprocore
油
Copy link &paste Google new tab > https://pcprocore.com/
IDM Crack with Internet Download Manager (IDM) is a tool to increase download speeds, resume, and schedule downloads.Comprehensive error recovery and resume capability will restart broken or interrupted downloads due to lost connections, network problems, computer shutdowns, or unexpected power outages. The simple graphic user interface makes IDM user-friendly and easy to use. Internet Download Manager has a smart download logic accelerator with intelligent dynamic file segmentation and safe multipart downloading technology to accelerate your downloads. Unlike other download managers and accelerators, Internet Download Manager segments downloaded files dynamically during the download process and reuses available connections without additional connect and login stages to achieve the best acceleration performance for IDM users.
System Requirements of IDM:
Operating System: Windows XP, NT, 2000, Vista, 7, 8, 8.1, 10 & 11 (32bit and 64bit)
Memory (RAM): 512 MB of RAM required
Hard Disk Space: 25 MB of free space required for full installation
Processor: Intel Pentium 4 Dual Core GHz or higher. Ensure your system meets these requirements for the IDM Crack to function properly.
How to Install and Crack:
Temporarily disable the antivirus until the IDM Crack process
Install idman642build41.exe
Extract IDM 6.42.41 Patch.rar (Password is: 123)
Install IDM 6.42.41 Patch.exe
Done!!! Enjoy!!!From Data Preparation to Inference: How Alluxio Speeds Up AI
From Data Preparation to Inference: How Alluxio Speeds Up AIAlluxio, Inc.
油
Alluxio Webinar
June 17, 2025
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
Jingwen Ouyang (Sr. Product Manager @ Alluxio)
In this talk, Jingwen Ouyang, Senior Product Manager at Alluxio, will share how Alluxio make it easy to share and manage data from any storage to any compute engine in any environment with high performance and low cost for your model training, model inference, and model distribution workload.Best MLM Compensation Plans for Network Marketing Success in 2025
Best MLM Compensation Plans for Network Marketing Success in 2025LETSCMS Pvt. Ltd.
油
Discover the top MLM compensation plans including Unilevel, Binary, Matrix, Board, and Australian Plans. Learn how to choose the best plan for your business growth with expert insights from MLM Trees. Explore hybrid models, payout strategies, and earning potential.
Learn more: https://www.mlmtrees.com/mlm-plans/
CodeCleaner: Mitigating Data Contamination for LLM Benchmarking
CodeCleaner: Mitigating Data Contamination for LLM Benchmarkingarabelatso
油
The pdf-version of "CodeCleaner: Mitigating Data Contamination for LLM Benchmarking" presented in Internetware 2025.Best AI-Powered Wearable Tech for Remote Health Monitoring in 2025
Best AI-Powered Wearable Tech for Remote Health Monitoring in 2025SEOLIFT - SEO Company London
油
Introduction In 2025, the fusion of artificial intelligence (AI) with wearable technology is redefining how we monitor health remotely. With the rise in chronic illnesses and the need for proactive health tracking, AI-powered wearables have emerged as essential tools. These devices offer real-time health insights, predictive alerts, and seamless integration with telehealth services.declaration of Variables and constants.pptx
declaration of Variables and constants.pptxmeemee7378
油
Rules of declaration of variables and constantsDownload Adobe Illustrator Crack free for Windows 2025?
Download Adobe Illustrator Crack free for Windows 2025?grete1122g
油
COPY & PASTE LINK https://click4pc.com/after-verification-click-go-to-download-page/
Adobe Illustrator CC Crack will make your illustration level upgrade by moving toward real modification purpose using adobe pro tools there ..Zonerankers Digital marketing solutions
Zonerankers Digital marketing solutionsreenashriee
油
Zoneranker offers expert digital marketing services tailored for businesses in Theni. From SEO and PPC to social media and content marketing, we help you grow online. Partner with us to boost visibility, leads, and sales.
Ad
Trasformare un'applicazione monolitica in microservices (versione #daje)
- 1. HOW TO DISASSEMBLE A MONOLITHIC APPS IN (NOT-SO) MICRO-SERVICES ROME 18 - 19 MARCH 2016
- 5. PARTNERS
- 7. DISCLAIMER my personal opinion people have different experiences ideas, comment, etc contact me @realfuzzy subject is wide, so Id love to hear your thoughts :-) Its not a code talk (but you can see some sources)
- 8. AGENDA:THERES NO AGENDA Ive got a tale instead
- 12. BUAHAHAHAHA! I AM THE MONOLITH! COME TO THE WORLD TO BRING IMMOBILISM AND COMPLEXITY!
- 13. THE MONOLITH
- 14. easy to develop
- 15. IDEs & development tools support
- 16. easy to test
- 17. simple to deploy
- 18. works well for relatively small apps
- 21. dif鍖cult to adopt new technologies
- 22. often stuck with the starting choices
- 23. doesnt scale to long-lived application
- 26. WHY MICROSERVICES suite of small services running in its own process communicating with lightweight mechanisms built around business capabilities independently automated deployable technology agnostic
- 29. relatively small
- 34. no vendor lock
- 36. - additional complexity of a distributed system - tools/IDEs are monolithic applications oriented - testing is more dif鍖cult - must implement the inter-service communication - increase memory consumption
- 37. AGENDA* whats a microservice? why have I to jump in ? where I can start from ? how I should be aware of ? * I know, I know, I lied about the agenda
- 38. Martin Fowler, Chief Scientist -ThoughtWorks dont even consider microservices unless you have a system that's too complex to manage as a monolith
- 40. Sam Newman, author of Building Microservices I remain convinced that it is much easier to partition an existing [] system than to do so up front You have more to work with.
- 44. Q0: HOW TO DECOMPOSE A MONOLITH? 1. Identify business boundaries 2. start decomposing each into own microservice 3. follow the Single Responsibility Principle 4. goto :2
- 46. Sir. Tools A warrior that can use every kind of tool as a weapon Strateky Sensei Master renowned for its strategic and tactical ability Workodoo Master The work-force is strong with this one
- 49. HAHAHAHA! YOUR EFFORTS ARE NOT ENOUGH TO DEFEAT ME!
- 50. Your efforts have little effect! an orthogonal approach might help you ...
- 54. CHOOSE WISELY Reliability Routing algorithms Highly Availability Supported protocols
- 55. OUR CHOICE RABBITMQ AMPQ message broker Erlang Fast, reliable, secure Many clients Commercial support
- 56. HERE!
- 57. SPECIFICATION IS A MUST (no matter what)
- 59. DESIGN FOR FAILURE aka: communicate when communication is hard
- 63. HOW IT LOOKS LIKE
- 64. 9XL
- 68. Melvin Conway, 1968 organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations
- 70. Martin Fowler, Chief Scientist -ThoughtWorks For many people throwing away a code base is a sign of failure, perhaps understandable , but still failure.
- 72. POLYGLOT IS NICE but mother tongue is fair enough
- 73. DEVOPS! no devops?!? no party. https://www.鍖ickr.com/photos/91657289@N02/10218392744
- 74. CONTINUOUS DEPLOYMENT FOR RUBY GEMS
- 75. The Smith Master craftsman expert in forging anything The Sculptor An artist able to give shape to magni鍖cent works The Painter Colors and shapes come to life on her canvas!
- 82. NO MONOLITHS WERE HARMED INTHE MAKING OFTHIS PRESENTATION
- 84. TAKEAWAYS go monolith 鍖rst communication (all-around) is strategic assets start simple, then dont fear the change take decisions, I-REALLY-MEAN-THAT
- 85. WHATS NEXT ? testing CQRS + ES log analisys & monitoring metrics