Micro-services Battle Scars

Nov 4, 20144 likes959 views

This document discusses microservices and some of the benefits and challenges of using a microservices architecture. It notes that microservices involve running many small, independent processes that communicate asynchronously via messages. Services can be developed and deployed independently, allowing for continuous deployment and improved scalability. However, microservices also introduce new challenges around service communication and coordination that require tools and best practices to address.

4 years of Node.js
50+ projects
startups to gorillas
1 user to 1 000 000
every kind team
all skill levels
nearForm ❤️ micro-services.
Richard Rodger @rjrodger

What do you think micro-services
are made of?

You run lots of little processes,
on many machines.

All services can see
All messages …
and react to the ones they care
about - a useful fiction!
Your services communicate using
asynchronous messages.

Messages are just JSON documents.
Patterns are just property-value pairs.
info:user, what:login
You use pattern-matching to
react to the right messages.

You get real software components.
Finally!

•re-usable
•which really means: composable
•extensible
•easy to add functionality
•encapsulated and loosely coupled
•the implementation does not leak
•well-defined interface
•but note: this does not mean strict!
Here’s what software components
should do for you.

How do you write micro-services
to handle this?

Write more micro-services when
you need to specialise.
Add more specific patterns for
more fine-grained functionality.
You always add services, never modify.
Pattern matching makes this work.

You get service composition
when you use pattern matching.

nodezoo.com - github.com/rjrodger/nodezoo
An example system big enough to be interesting.


PILE OF POO
U+1F4A9
You can get yourself into trouble
with micro-services…

You may get a rash of little web servers.
This never ends well.

Define a schema for the
properties of the Chair entity.
Make sure you cover all
the business cases!
Jon Postel: You should be liberal in
what you accept, and strict in what you emit.

You can never get away
from some anti-patterns.

You can use any language!
What could possibly go wrong?

Architecture. The boxes and arrows
don’t work anymore.
You’ll discover more services
than you’ll design.

Don’t keep any state in your services.
We’ve tried that already with OOP.
It doesn’t work.
You use micro-services to perform actions.
They don’t describe the world.

You’ll need practice.
Micro-services break lots of rules.


ROCKET
U+1F680
You can be awesome
with micro-services.

You can swap databases mid-project!
Or anything else. Infinite Power!

You can actually do continuous deployment!
Micro-services are the “unit of deployment”.

You can verify new micro-service versions work
by running them beside old versions.

senecajs.org nearform.com/nscale
nodejs.org docker.com
You’ll need some tools to make this work.

This document discusses measuring microservices by monitoring message flow rates and patterns. It suggests measuring: - Message flow rates after deploying new services to detect any breaks - Common message patterns like actor, subscriber, chain, and tree to validate expected behavior - Invariants like the relationship between add-item and sales-tax messages to ensure the system is functioning correctly Measuring these things provides visibility into the health and risks of the distributed system.

Richardrodger nodeday-2014-finalRichard Rodger

Enterprise software teams are starting to understand and embrace the power of Node.js. They face a serious challenge: integrating Node.js into the legacy systems they maintain, and migrating these system over time into Node.js architectures. This talk is a pathfinder for those facing this task. As a community we must proactively engage with the Java and .Net communities, and create a deeper understanding of the "Node.js Way".

Richardrodger nodeconfeu-2014-finalRichard Rodger

How microservices fail, and what to do about itRichard Rodger

Cleaning up your codebase with a clean architectureBarry O Sullivan

A talk I gave at the WaterfordTech meetup on 26/07/2017. The talk focusses on the problem of writing good code, why do we find it so hard? Once we understand the problem, we can look at solutions, and then we focus on how a clean architecture can be applied to give us that first step of clarity that leads to good code. The code used in the examples can also be found here (use arrow keys to navigate pages) https://barryosull.github.io/clean-architecture-code.html

From a web application to a distributed systemGianluca Padovani

Design patterns - The Good, the Bad, and the Anti-PatternBarry O Sullivan

Serverless lessons learned #5 retriesMaik Wiesmüller

When we started building serverless applications back in 2017, there was quite a lot to learn. So we'd like to share some mistakes, important pieces, and concepts for production-ready serverless projects. This time: Retries. More Information: API-Retries: https://lnkd.in/dVwwEsat Lambda-Retries: https://lnkd.in/dEs6xXyb SQS-Retries: https://lnkd.in/dPm2x7ZT

Design Patterns in Micro-services architectures & GilmourPiyush Verma

This document provides an overview of design patterns in microservices architectures using Gilmour, an open-source library for building distributed systems. Key topics covered include request-response and asynchronous communication patterns, service discovery and load balancing without an external process, error handling, monitoring, and service composition capabilities for building complex workflows from simpler microservices. Examples demonstrated include echo clients and servers, popular word counting from text, and weather data aggregation across multiple services.

micro services architecture (FrosCon2014)smancke

Vertical thinking for a simple architecture! Micro Services are a new way of architectural thinking in web platforms. The key idea is strongly aligned on the unix philosophy: Create small services which are only responsible for one thing and make them work together. With this in mind, you get simple applications, which can be developed, deployed and scaled independent from each other. The key challenge in using micro services is to decompose applications vertically, by their functional domains. Only with this, you are able to reduce dependencies and create simple applications. On a technical side, micro services are backed by a wide support in different programming languages and open source frameworks. Especially the state of the art deployment mechanisms make this approach possible at all.

Towards Realizing Dynamic QoS-aware Web Service CompositionGeorge Baryannis

In this presentation, we identify two major issues related to Web service composition: the lack of formal specifications for services and service compositions and the inability of current service composition approaches to support dynamicity and QoS-awareness in an effective and scalable way. We analyze the underlying research challenges for each of these issues and propose a tentative research plan to address them.

Load balancing theory and practiceFoundationDB

Load balancing aims to distribute work across multiple computers to optimize resource utilization and system performance. It involves techniques to minimize response times and avoid overloading parts of the system. A key consideration is the latency curve, which shows how latency increases as load approaches saturation. Load balancing strategies aim to keep latency low even at high loads by balancing work distribution. Queuing theory concepts like Little's Law, which relates queue size, arrival rate and wait time, can provide insights for analyzing and improving load balancing approaches.

Delivering with Microservices - How to Iterate Towards SophisticationThoughtworks

A microservices architecture requires some complex engineering. So when choosing microservices, a software engineering team must be prepared to tackle some challenges early in the project. On the other hand, an Agile approach requires the team to focus on delivering business value from Iteration 1. The fully-featured architecture of the solution will not emerge until later. While clear and strong technical choices must be made early in a microservices project, how do you resist the temptation of building the infrastructure first? In this presentation, Jean Robert D'Amore talks about the tools and techniques you can use to let your product evolve towards a microservices architecture, while setting up the team for success.

Netflix security monkey overviewRyan Hodgin

Scalable Microservices at Netflix. Challenges and Tools of the TradeC4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1A8mYn2. Sudhir Tonse discusses about the robust interprocess communications (IPC) framework that Netflix built (Ribbon). Filmed at qconsf.com. Sudhir Tonse manages the Cloud Platform Infrastructure team at Netflix and is responsible for many of the services and components that form the Netflix Cloud Platform as a Service.

Mastering Chaos - A Netflix Guide to MicroservicesJosh Evans

QConSF 2016 Abstract: By embracing the tension between order and chaos and applying a healthy mix of discipline and surrender Netflix reliably operates microservices in the cloud at scale. But every lesson learned and solution developed over the last seven years was born out of pain for us and our customers. Even today we remain vigilant as we evolve our service architecture. For those just starting the microservices journey these lessons and solutions provide a blueprint for success. In this talk we’ll explore the chaotic and vibrant world of microservices at Netflix. We’ll start with the basics - the anatomy of a microservice, the challenges around distributed systems, and the benefits realized when integrated operational practices and technical solutions are properly leveraged. Then we’ll build on that foundation exploring the cultural, architectural, and operational methods that lead to microservice mastery.

Pros and Cons of a MicroServices Architecture talk at AWS ReInventSudhir Tonse

Netflix morphed from a private datacenter based monolithic application into a cloud based Microservices architecture. This talk highlights the pros and cons of building software applications as suites of independently deployable services, as well as practical approaches for overcoming challenges - especially in the context of an elastic but ephemeral cloud ecosystem. What were the lessons learned while building and managing these services? What are the best practices and anti-patterns?

Developing applications with a microservice architecture (SVforum, microservi...Chris Richardson

The Big Picture - Integrating BuzzwordsAlessandro Giorgetti

Slides for the session presented at the "Un Actor (Model) per amico - multithreading made easy" DevMarche User group event. In the talk I introduced many of the techniques and practices the teams I work with use when it comes to design and develop highly concurrent and possibly distributed applications. I also tried to show how many of the concepts coming from several "sources", like Agile practices, DDD, SOA, Microservices, Actor Model, etc overlap and integrate to reach the goal of modelling a working solution for our customers.

Let's talk about... MicroservicesAlessandro Giorgetti

Richardrodger nodeday-2014-finalRichard Rodger

This talk is an appeal to server-side JavaScript developers to make use of this time of change - Node.js is going to become the primary server-side platform for most developers. We can move forward from the old way of building web apps as large inter-locking co-dependent code bases. The Node.js module system has shown us the way. It's the first step. Now, we need to use the beauty of Node modules to help us build robust, scalable apps. This approach is called the Micro-Services Architecture. It's more than just having some services with HTTP end-points. It's about taking this to the extreme. Everything is a service, and no service is larger than 100 lines of code. We've been using this approach for most of our projects for the last 18 months and it works really well. We get to drop loads of project management ceremony. There will be some customer war stories.

DevOps 201607 Vishwanath Ramdas

From 🤦 to 🐿️Ori Pekelman

Slides from my DevOpsExpo London talk "From oops to NoOps". They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions. It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise. We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously. At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability. In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.

The working architecture of NodeJS applications, Виктор ТурскийSigma Software

The document discusses the working architecture of NodeJs applications. It begins by introducing the speaker Viktor Turskyi and his experience. It then discusses why architecture is important and shares their battle-tested approach. The presentation addresses whether to use monolith or microservices architectures, and recommends starting with a monolith in most cases. It also discusses domain models, services, and controllers. The presentation provides an example of a service class and user registration process to demonstrate the architecture in practice.

The working architecture of node js applications open tech week javascript ...Viktor Turskyi

Javascript spaghetti stirtrek_5_17Jared Faris

This document discusses how to build rich user experiences with JavaScript without creating "spaghetti code". It advocates for pushing events rather than state between components, writing small discrete bits of code, and fully decoupling components. Specific techniques mentioned include using design patterns like mediator and observer, frameworks like Knockout and Backbone, namespacing, inheritance, and testing isolated layers. The goal is to structure JavaScript applications similarly to server-side code by treating the client-side seriously and applying best practices around modularity and loose coupling.

RedisConf18 - Common Redis Use Cases for Cloud Native Apps and MicroservicesRedis Labs

The document discusses cloud native applications and architectures. It explains that cloud native applications are designed to take advantage of cloud computing abilities like scaling up and down on demand and limitless compute. Being cloud native isn't just an architectural pattern but a combination of practices like agile development, continuous delivery, automation, containers, and microservices that change development culture and move to a DevOps model. It also discusses concepts like serverless computing, functions as a service, microservices, and twelve factor applications.

Moving to Microservices with the Help of Distributed TracesKP Kaiser

Moving away from a monolith to a microservices architecture is a process fraught with hidden challenges. There's legacy code, infrastructure, and organizational processes that all need to change, in order to make the switch successful. But microservices come with a huge increase in infrastructure complexity. We'll see how distributed traces empower developers to work with greater autonomy, in increasingly complex deployment environments.

Php ruleschristopher mabunda

The document provides 10 rules for PHP development: 1) Use object-oriented programming (OOP) as it is faster, simpler and uses less server resources than procedural programming. 2) Avoid functions ending in "_once()" as they are hard on server resources. 3) Develop with full error reporting turned on to catch errors early. 4) Use PHP's built-in functions where possible instead of writing custom code. 5) Protect databases by escaping all strings and validating input before queries. 6) Use POST instead of GET to submit forms for added security. 7) Plan projects before coding by wireframing or taking notes. 8) Fully understand a project before developing it.

QCon 2015 - Microservices Track Notes Abdul Basit Munda

More Related Content

Viewers also liked (10)

Design Patterns in Micro-services architectures & GilmourPiyush Verma

micro services architecture (FrosCon2014)smancke

Towards Realizing Dynamic QoS-aware Web Service CompositionGeorge Baryannis

Load balancing theory and practiceFoundationDB

Delivering with Microservices - How to Iterate Towards SophisticationThoughtworks

Netflix security monkey overviewRyan Hodgin

Scalable Microservices at Netflix. Challenges and Tools of the TradeC4Media

Mastering Chaos - A Netflix Guide to MicroservicesJosh Evans

Pros and Cons of a MicroServices Architecture talk at AWS ReInventSudhir Tonse

Developing applications with a microservice architecture (SVforum, microservi...Chris Richardson

Design Patterns in Micro-services architectures & GilmourPiyush Verma

micro services architecture (FrosCon2014)smancke

Towards Realizing Dynamic QoS-aware Web Service CompositionGeorge Baryannis

Load balancing theory and practiceFoundationDB

Delivering with Microservices - How to Iterate Towards SophisticationThoughtworks

Netflix security monkey overviewRyan Hodgin

Scalable Microservices at Netflix. Challenges and Tools of the TradeC4Media

Mastering Chaos - A Netflix Guide to MicroservicesJosh Evans

Pros and Cons of a MicroServices Architecture talk at AWS ReInventSudhir Tonse

Developing applications with a microservice architecture (SVforum, microservi...Chris Richardson

Similar to Micro-services Battle Scars (20)

The Big Picture - Integrating BuzzwordsAlessandro Giorgetti

Let's talk about... MicroservicesAlessandro Giorgetti

Richardrodger nodeday-2014-finalRichard Rodger

DevOps 201607 Vishwanath Ramdas

From 🤦 to 🐿️Ori Pekelman

The working architecture of NodeJS applications, Виктор ТурскийSigma Software

The working architecture of node js applications open tech week javascript ...Viktor Turskyi

Javascript spaghetti stirtrek_5_17Jared Faris

RedisConf18 - Common Redis Use Cases for Cloud Native Apps and MicroservicesRedis Labs

Moving to Microservices with the Help of Distributed TracesKP Kaiser

Php ruleschristopher mabunda

QCon 2015 - Microservices Track Notes Abdul Basit Munda

Pareto will tell you to stop using your ORM - Mateo CollinaWey Wey Web

This document discusses choosing technologies for software projects. It argues that ORMs do not scale well and promote spaghetti code because models take on too many responsibilities. Modular monoliths and microservices help address these issues by separating concerns. The author promotes Platformatic as a tool that can remove repetitive tasks while still allowing complex features by extending databases through code.

Microservices rubyconf-2013Mohit Thatte

- Microservices are small, independent services that each perform a single function. They communicate through well-defined interfaces using protocols like HTTP. This allows for independent development and scaling of each service. - The advantages of microservices include increased flexibility, scalability, and allowing a system to evolve more easily. However, they also introduce more complex infrastructure requirements and can result in fragmented data. - The presentation provides examples of how microservices can be implemented incrementally by starting with high-level services and extracting smaller ones over time as needed. It also emphasizes the importance of testing, automation, and other DevOps practices for managing microservices architectures.

Php ruleschristopher mabunda

The document provides 10 tips for PHP development: 1) Use object-oriented programming (OOP) for its advantages over procedural programming. 2) Avoid functions ending in "_once()" as they are hard on server resources. 3) Develop with error reporting turned on to catch errors early. 4) Use PHP's built-in functions instead of writing your own code when possible. 5) Protect databases by sanitizing input and validating data types before queries. 6) Use POST instead of GET to submit forms for added security. 7) Plan projects before coding by wireframing or taking notes. 8) Fully understand a project before developing it. 9) Improve coding skills

From DevOps to NoOps how not to get Equifaxed ApidaysOri Pekelman

Flow: A living full-stack framework for the websebastian sastre

Simple Object Oriented Design (MEAP V04) Mauricio Anichegolemtillo

What linq is aboutLeTesteur

The document provides an overview of LINQ (Language Integrated Query) and how it allows developers to more declaratively work with data in C# and other imperative languages. It discusses how LINQ expressions are composed of expression trees that can be executed in different ways, including locally in memory with LINQ to Objects, or pushed to a database with LINQ to SQL. It also shows how LINQ expressions can be made parallel using constructs like AsParallel() and executed across multiple machines with frameworks like DryadLINQ.

Evolving your api architecture with the strangler patterndwcarter74

The Big Picture - Integrating BuzzwordsAlessandro Giorgetti

Let's talk about... MicroservicesAlessandro Giorgetti

Richardrodger nodeday-2014-finalRichard Rodger

DevOps 201607 Vishwanath Ramdas

From 🤦 to 🐿️Ori Pekelman

The working architecture of NodeJS applications, Виктор ТурскийSigma Software

The working architecture of node js applications open tech week javascript ...Viktor Turskyi

Javascript spaghetti stirtrek_5_17Jared Faris

RedisConf18 - Common Redis Use Cases for Cloud Native Apps and MicroservicesRedis Labs

Moving to Microservices with the Help of Distributed TracesKP Kaiser

Php ruleschristopher mabunda

QCon 2015 - Microservices Track Notes Abdul Basit Munda

Pareto will tell you to stop using your ORM - Mateo CollinaWey Wey Web

Microservices rubyconf-2013Mohit Thatte

Php ruleschristopher mabunda

From DevOps to NoOps how not to get Equifaxed ApidaysOri Pekelman

Flow: A living full-stack framework for the websebastian sastre

Simple Object Oriented Design (MEAP V04) Mauricio Anichegolemtillo

What linq is aboutLeTesteur

Evolving your api architecture with the strangler patterndwcarter74

More from Richard Rodger (20)

Using RAG to create your own Podcast conversations.pdfRichard Rodger

The presentation on "Retrieval Augmented Generation for Interactive Podcasts" outlines a method to transform podcast audio into interactive chat interfaces. It covers the design, coding, and practical aspects of using Retrieval Augmented Generation (RAG) to emulate podcast guest responses. The project involves processing a significant volume of podcast data, including episodes, transcripts, and metadata. The technical discussion focuses on ingesting audio and metadata into an AI system and querying it for conversational responses. Key concepts introduced include vector embedding, which converts text to conceptual vectors using models, and the application of Large Language Models (LLMs) with Transformer architecture for context understanding. The coding segment details microservice messages for transcript ingestion and chat functionalities, employing transcription services, embedding techniques, and vector storage solutions. Challenges in RAG project deployment are also discussed, highlighting performance, quality, regressions, and managing expectations. The presentation concludes by contrasting technical complexities with a philosophical vision of AI's potential, inspired by speculative fiction, suggesting a future where AI capabilities vastly exceed human cognitive functions. Further resources and open-source implementations are provided for those interested in the technical development of interactive podcast systems

Richard_TheDev2023_pattern.pptx.pdfRichard Rodger

The presentation addresses the challenges developers face with APIs, such as the diversity in authentication methods, SDKs, and the steep learning curve for each new API. The key proposition is to approach API interactions through an ORM-like abstraction, treating APIs as databases to simplify CRUD operations and action commands. The core idea revolves around treating everything as a message, leveraging microservices as modular, independent components that communicate through these messages. This approach enables a uniform way to interact with various APIs by encapsulating the complexities behind simple, standardized message formats. The example provided illustrates how updating a GitHub repository's description can be abstracted into a message, streamlining the process. This methodology promotes a component-based architecture where microservices, defined by their ability to handle specific message patterns, can be composed to achieve more complex functionalities. The presentation outlines how this model can be applied to the GitHub API, transforming traditional API calls into message-driven interactions, thereby achieving a higher level of abstraction and simplicity. The benefits of this approach include a unified interface for API calls, reduction in the reliance on multiple SDKs, and the facilitation of "pure" business logic that focuses on entity manipulation rather than the intricacies of API communication. The presentation concludes with practical considerations for implementation, such as handling logistics and edge cases, and offers resources for further exploration, emphasizing the philosophy of reducing unnecessary complexity in software design.

richard-rodger-awssofia-microservices-2019.pdfRichard Rodger

This presentation shares the journey of voxgig, a Software-as-a-Service platform for conference exhibitors, and its strategic decision to adopt microservices from the outset. The narrative unfolds with an exploration of how a small, remote team can build a significant platform, detailing a development timeline that spans from initial exploration to platform launch, all structured around microservices. The architecture of voxgig is dissected to reveal two pivotal tactics: Transport Independence and Pattern Matching, which collectively enable emergent design within the microservices ecosystem. These concepts are expanded to illustrate their role in facilitating service distribution, extension, specialization, and composition, laying the groundwork for a robust microservice architecture. Despite aspiring to an ideal microservice structure characterized by clean separation between client, application, and core data layers, practical challenges lead to a more organic coding approach, often necessitating later technical debt repayment. The evolution of voxgig's architecture culminates in a diverse ecosystem of 65 Node.js services, enriched by a detailed statistical analysis highlighting service size, age, quality, and the overarching message patterns that constitute the system's backbone. Key lessons emerge from voxgig's experience, underscoring the complexity of UX design, the importance of adhering to one's methodologies, and the value of investing time in a robust core system. Insights into operational efficiencies, such as service bundling for cost savings and the indispensability of a message REPL, are shared. The presentation concludes by emphasizing the critical role of components within the microservices framework, advocating for system-wide operability in a single process locally and the pragmatic use of synchronous messages for the majority of use cases, all while championing the concept of microservices as fundamental components of a scalable, agile architecture.

richardrodger-microservice-algebra-cluj-apr.pdfRichard Rodger

This presentation delves into the mathematical principles underpinning microservices, drawing inspiration from historical numeral systems to illustrate the significance of adopting efficient mental models in software architecture. By contrasting the complexities of Roman numerals with the streamlined Indian numerical system, the talk sets the stage for rethinking software design through an algebraic lens, where microservices are seen as algebraic functions transforming inputs to outputs, akin to CRUD operations. The core idea revolves around conceptualizing microservices as operations on messages, ensuring seamless service integration within complex systems through transport independence and pattern matching. This approach fosters a loosely coupled architecture where services communicate based on message content rather than direct identities, enhancing system flexibility and scalability. Practical examples, including the development of a Node.js module search engine, demonstrate the application of these concepts, showcasing the ease of system expansion and modification when services are designed to interact through a message-driven paradigm. The presentation concludes by underscoring the benefits of this methodology, such as increased system adaptability, easier management of technical debt, and a more granular approach to system evolution, advocating for a shift towards viewing microservices as integral components of a coherent and scalable system architecture.

richardrodger-designing-microservices-london-may.pdfRichard Rodger

In this thought-provoking session at mucon London 2018, the dialogue revolves around the foundational premise that microservices should be embraced from the inception of a project, irrespective of the organization's size, from startups to established enterprises. The discussion opens with a candid acknowledgment of the inherent challenges in software engineering across the board, probing into the reasons behind the perceived complexity of software development, our collective penchant for perfection, and the frequent overemphasis on process over product. The narrative then shifts to a more philosophical perspective, positioning microservices as the optimal intersection of psychological comfort and engineering pragmatism, conceptualized as units of quality, trust, and business logic encapsulation. This conceptual framework underpins a series of tactical recommendations, advocating for a message-centric approach to system design, where the delineation between monoliths, microservices, and serverless architectures blurs in favor of seamless communication and interoperability. Practical advice is offered on tackling the 'general case' in system design, encouraging the development of specialized services for outlier scenarios and promoting adaptability to change. However, this approach is not without its trade-offs, sparking a debate on the merits and pitfalls of repository strategies and the double-edged sword that is Kubernetes, juxtaposed against the benefits such as finely segmented technical debt, deferred decision-making, and the capacity to scale rapidly without extensive cross-team coordination. The session concludes on a reflective note, inviting attendees to explore further resources such as senecajs.org and "The Tao of Microservices", leaving the audience with a nuanced understanding of microservices as not just a technological choice, but a strategic framework for building resilient, adaptable, and business-aligned software ecosystems.

richardrodger-designing-microservices-london-may.pdfRichard Rodger

This presentation introduces a systematic approach to designing microservices using a visual language, beginning with the identification of requirements and distillation into messages that dictate service interactions. The methodology is illustrated through the process of developing a user registration system, breaking down the requirements into discrete messages like 'register-user' and 'confirm-email', which in turn inform the design of specific services handling registration and email confirmation. The discussion extends to the temporal and functional dynamics of microservice interactions, differentiating between synchronous and asynchronous, as well as consumed and observed messages, using a unique visual lexicon where hexagons represent microservices, solid and dashed lines denote synchronous and asynchronous communications, and arrow styles distinguish between message consumption and observation. The narrative further concretizes these concepts by outlining the design of a Node.js module search engine, showcasing how business requirements translate into a network of microservices handling search, indexing, and module detail presentation. The intricate web of service interactions is depicted through the visual language, demonstrating how services like 'web', 'search', 'npm', and 'github' collaborate through well-defined message patterns. By the conclusion, attendees are equipped with a versatile framework for microservice design, capable of transforming complex system requirements into clear, manageable service components, as exemplified by the 'nodezoo' search engine project. This methodological approach not only clarifies the architecture of microservices systems but also facilitates their scalability, maintainability, and evolution over time.

richardrodger-microservice-risk-dublin-mar.pdfRichard Rodger

This presentation delves into the intricate balance of risks and rewards in adopting microservices architecture, drawing parallels between complex systems failures, like the Three Mile Island nuclear incident, and potential pitfalls in software systems. It underscores the inherent risk in systems composed of multiple dependent components, highlighting how increased component count amplifies failure likelihood, challenging the conventional wisdom that redundancy can safeguard against systemic flaws due to homogeneity in components. The discourse shifts to pragmatic strategies for managing deployment risks in microservices environments, advocating for frequent, low-impact deployments to mitigate the consequences of inevitable errors, as opposed to infrequent, high-stakes updates. The speaker presents microservices as a solution that simplifies deployments by isolating changes to individual components, thereby enhancing system reliability. The emphasis is placed on monitoring message flow rates as vital indicators of system health, with various microservice patterns like Actor, Subscriber, Chain, and Tree explored to illustrate message distribution dynamics. The presentation concludes with practical deployment strategies like Canary and Progressive Canary releases, along with the concept of "Bake" deployments to incrementally expose new features, using these methods as risk measurement tools within the continuous delivery pipeline. The talk encourages embracing measured, data-driven approaches and automation to navigate the complexities of microservice deployments effectively, ensuring that technology adheres to the unforgiving principles of reality over theoretical perfection.

richardrodger-service-discovery-waterford-feb.pdfRichard Rodger

Title: Rethinking Service Discovery in Microservices Architecture Description: This presentation delves into the microservices architectural pattern, emphasizing the importance of service discovery in a landscape where services operate under the illusion of being solitary entities in the system. The discussion begins with an overview of microservices — small, independent processes that communicate through messages, which collectively contribute to a robust component model facilitating rapid development, continuous delivery, and the mitigation of technical debt. The core of the talk addresses the complexities and unconventional programming models introduced by microservices, particularly focusing on the challenge of service-to-service discovery. Various strategies for service discovery are explored, including the use of configuration files, intelligent load balancing, service registries, DNS, and the necessity of a message bus. The concept of service discovery is then critically examined, proposing a paradigm shift towards pattern matching, where services interact based on message patterns rather than service identities. This approach advocates for transport independence, blind messaging, and a peer-to-peer model, where services maintain a local worldview, updated dynamically as services fluctuate. The presentation concludes by introducing the SWIM algorithm, an infection-style process group membership protocol designed for scalability and weak consistency, exemplified through a practical implementation in a Twitter clone built with 14 microservices.

richardrodger-vespa-waterford-oct.pdfRichard Rodger

Explore the cutting-edge capabilities of Vespa.ai, the open-source search engine pioneered by Yahoo, now a cornerstone for developers and data scientists seeking enhanced search and analytics functionalities. This session delves into the integration of machine learning to elevate search accuracy and user experience, achieving a fine balance between precision and recall. Participants will gain insight into Vespa.ai's evolution towards a cloud-based, analytics-focused platform, offering extensive configurability for Java aficionados and seamless incorporation of database-free text search capabilities. The presentation further highlights the operational advantages and development efficiencies of Vespa.ai, including its compatibility with major big data technologies, automatic load distribution, and scalable deployment options. Attendees will leave with a comprehensive understanding of leveraging Vespa.ai for sophisticated, personalized search solutions within their own applications or platforms.

Richardrodger designing-microservices-uxdx-dublin-octRichard Rodger

The document discusses how to design microservices for an application. It explains that microservices should contain independent and similar pieces of functionality that can run in any order, unlike monolithic enterprise applications where components depend on each other in a specific order. The document then uses a search engine as an example, showing how the requirements can be broken down into independent microservices for querying, retrieving details, and handling synchronous vs. asynchronous requests.

Rapid Digital Innovation: How Node.js DeliversRichard Rodger

Node.js allows for rapid digital innovation by enabling rapid feedback cycles and using data to guide iterations. It breaks down barriers to innovation by delivering value early. Projects can be delivered in half the time compared to traditional platforms due to Node.js requiring less code and being easier to change. Node.js is also well suited for microservices architectures. A case study described a digital transformation initiative for multiple companies across countries that was delivered using Node.js within a tight 12 week deadline by a small distributed team, despite many challenges.

Richard rodger technical debt - web summit 2013Richard Rodger

The only way developers can finish projects on-time and under-budget is by taking on Technical Debt. Taking shortcuts, using quick fixes, and writing unmaintainable code builds up a technical debt that get the project delivered today. Tomorrow, there will be a reckoning, as development costs spiral and progress grinds to a halt. This talk helps you embrace the debt, love the cowboys, and gives you a way to make repayments.

The Seneca Pattern at EngineYard Distill 2013 ConferenceRichard Rodger

The document discusses building large applications using a pattern matching approach with microservices. Small independent processes communicate via asynchronous messages to perform actions like saving or retrieving data, deploying applications, and routing requests. This approach allows for easy scaling, language independence between processes, and a shared mental model based on patterns that is intuitive for both humans and machines.

Building businesspost.ie using Node.jsRichard Rodger

This document discusses lessons learned from building JavaScript applications. It finds that client-side JavaScript is very challenging due to the need to support multiple browsers. It recommends using a framework like Backbone.js and keeping business logic in common code. Multi-platform HTML and CSS are also difficult due to varying browser support for CSS3 and media queries. The document notes that app stores present challenges different than websites, like inability to deploy hotfixes. It finds Node.js very capable but callbacks can be tricky. Overall it emphasizes planning for variations in browsers and platforms.

How to Write Big Apps (Richard Rodger NodeDublin 2012)Richard Rodger

The document provides an overview of different approaches to building applications in JavaScript - classical, prototypical, and functional programming styles. It then discusses using a pattern-based command approach instead of classes to build applications. The key benefits of the command approach include easy testing, distributed capabilities, decoupling of code, support for plugins, and overall control and organization of an application's business logic through defining commands. The talk concludes by demonstrating how to define and call commands using the Seneca library, which supports this pattern-based architecture for building applications.

Richard rodger-appgen-2012-lxjs-lisbonRichard Rodger

The document discusses how to generate multiple versions of apps from a single codebase for cross-platform development. It introduces a process of defining resources, transforms, and settings that get fed into forks to produce different app variations. An open-source tool called AppGen is presented as an implementation of this approach, allowing developers to write specification files that define the generation steps to produce multiple app versions. The document argues AppGen is useful when needing to build many similar apps, support different configurations, or create cross-platform HTML5 applications from a common codebase.

20120802 timisoaraRichard Rodger

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine that allows for writing server-side code in JavaScript. It has a single-threaded, event-driven architecture that makes it efficient for data-intensive real-time applications. Some key advantages of Node.js include using JavaScript for both client-side and server-side code, high performance due to event-driven and non-blocking model, and rich ecosystem of third-party modules. Mobile web apps can be built with Node.js by using HTML5 features and JavaScript on the server and client sides.

20120816 nodejsdublinRichard Rodger

The document discusses starting a Node.js community project called Seneca. Seneca is described as a toolkit that allows building a startup MVP in a weekend. It encourages participants to sign up via Twitter or email and contribute code to the GitHub repository. The document provides an overview of Node.js modules and how they work, and promotes contributing to the Seneca project by writing plugins and documentation.

20120306 dublin jsRichard Rodger

The document discusses how JavaScript can be used from the user interface on mobile and web apps through to the server and database using techniques like Node.js. It provides examples of how Node.js allows for high performance server-side JavaScript and how MongoDB can be used as a database. The document outlines lessons learned around challenges of multi-platform development and benefits of outsourcing databases and other services.

20120514 nodejsdublinRichard Rodger

The document introduces Node.js, a platform that allows developers to build server-side applications using JavaScript. It discusses how Node.js uses the Google Chrome V8 engine to run JavaScript code, provides a module system for third-party code, and allows applications to handle many concurrent connections through non-blocking and event-driven programming. Examples are given of how to write a simple web server in Node.js JavaScript code.

Using RAG to create your own Podcast conversations.pdfRichard Rodger

Richard_TheDev2023_pattern.pptx.pdfRichard Rodger

richard-rodger-awssofia-microservices-2019.pdfRichard Rodger

richardrodger-microservice-algebra-cluj-apr.pdfRichard Rodger

richardrodger-designing-microservices-london-may.pdfRichard Rodger

richardrodger-microservice-risk-dublin-mar.pdfRichard Rodger

richardrodger-service-discovery-waterford-feb.pdfRichard Rodger

richardrodger-vespa-waterford-oct.pdfRichard Rodger

Richardrodger designing-microservices-uxdx-dublin-octRichard Rodger

Rapid Digital Innovation: How Node.js DeliversRichard Rodger

Richard rodger technical debt - web summit 2013Richard Rodger

The Seneca Pattern at EngineYard Distill 2013 ConferenceRichard Rodger

Building businesspost.ie using Node.jsRichard Rodger

How to Write Big Apps (Richard Rodger NodeDublin 2012)Richard Rodger

Richard rodger-appgen-2012-lxjs-lisbonRichard Rodger

20120802 timisoaraRichard Rodger

20120816 nodejsdublinRichard Rodger

20120306 dublin jsRichard Rodger

20120514 nodejsdublinRichard Rodger

Recently uploaded (20)

FL Studio Producer Edition Crack 2025 Full Versiontahirabibi60507

Secure Test Infrastructure: The Backbone of Trustworthy Software DevelopmentShubham Joshi

Download YouTube By Click 2025 Free Full Activatedsaniamalik72555

Adobe Marketo Engage Champion Deep Dive - SFDC CRM Synch V2 & Usage DashboardsBradBedford3

Join Ajay Sarpal and Miray Vu to learn about key Marketo Engage enhancements. Discover improved in-app Salesforce CRM connector statistics for easy monitoring of sync health and throughput. Explore new Salesforce CRM Synch Dashboards providing up-to-date insights into weekly activity usage, thresholds, and limits with drill-down capabilities. Learn about proactive notifications for both Salesforce CRM sync and product usage overages. Get an update on improved Salesforce CRM synch scale and reliability coming in Q2 2025. Key Takeaways: Improved Salesforce CRM User Experience: Learn how self-service visibility enhances satisfaction. Utilize Salesforce CRM Synch Dashboards: Explore real-time weekly activity data. Monitor Performance Against Limits: See threshold limits for each product level. Get Usage Over-Limit Alerts: Receive notifications for exceeding thresholds. Learn About Improved Salesforce CRM Scale: Understand upcoming cloud-based incremental sync.

LEARN SEO AND INCREASE YOUR KNOWLDGE IN SOFTWARE INDUSTRYNidaFarooq10

WinRAR Crack for Windows (100% Working 2025)sh607827

Adobe Master Collection CC Crack Advance Version 2025kashifyounis067

🌍📱👉COPY LINK & PASTE ON GOOGLE http://drfiles.net/ 👈🌍 Adobe Master Collection CC (Creative Cloud) is a comprehensive subscription-based package that bundles virtually all of Adobe's creative software applications. It provides access to a wide range of tools for graphic design, video editing, web development, photography, and more. Essentially, it's a one-stop-shop for creatives needing a broad set of professional tools. Key Features and Benefits: All-in-one access: The Master Collection includes apps like Photoshop, Illustrator, InDesign, Premiere Pro, After Effects, Audition, and many others. Subscription-based: You pay a recurring fee for access to the latest versions of all the software, including new features and updates. Comprehensive suite: It offers tools for a wide variety of creative tasks, from photo editing and illustration to video editing and web development. Cloud integration: Creative Cloud provides cloud storage, asset sharing, and collaboration features. Comparison to CS6: While Adobe Creative Suite 6 (CS6) was a one-time purchase version of the software, Adobe Creative Cloud (CC) is a subscription service. CC offers access to the latest versions, regular updates, and cloud integration, while CS6 is no longer updated. Examples of included software: Adobe Photoshop: For image editing and manipulation. Adobe Illustrator: For vector graphics and illustration. Adobe InDesign: For page layout and desktop publishing. Adobe Premiere Pro: For video editing and post-production. Adobe After Effects: For visual effects and motion graphics. Adobe Audition: For audio editing and mixing.

Why Orangescrum Is a Game Changer for Construction Companies in 2025Orangescrum

Scaling GraphRAG: Efficient Knowledge Retrieval for Enterprise AIdanshalev

If we were building a GenAI stack today, we'd start with one question: Can your retrieval system handle multi-hop logic? Trick question, b/c most can’t. They treat retrieval as nearest-neighbor search. Today, we discussed scaling #GraphRAG at AWS DevOps Day, and the takeaway is clear: VectorRAG is naive, lacks domain awareness, and can’t handle full dataset retrieval. GraphRAG builds a knowledge graph from source documents, allowing for a deeper understanding of the data + higher accuracy.

PDF Reader Pro Crack Latest Version FREE Download 2025mu394968

🌍📱👉COPY LINK & PASTE ON GOOGLE https://dr-kain-geera.info/👈🌍 PDF Reader Pro is a software application, often referred to as an AI-powered PDF editor and converter, designed for viewing, editing, annotating, and managing PDF files. It supports various PDF functionalities like merging, splitting, converting, and protecting PDFs. Additionally, it can handle tasks such as creating fillable forms, adding digital signatures, and performing optical character recognition (OCR).

How to Batch Export Lotus Notes NSF Emails to Outlook PST Easily?steaveroggers

Migrating from Lotus Notes to Outlook can be a complex and time-consuming task, especially when dealing with large volumes of NSF emails. This presentation provides a complete guide on how to batch export Lotus Notes NSF emails to Outlook PST format quickly and securely. It highlights the challenges of manual methods, the benefits of using an automated tool, and introduces eSoftTools NSF to PST Converter Software — a reliable solution designed to handle bulk email migrations efficiently. Learn about the software’s key features, step-by-step export process, system requirements, and how it ensures 100% data accuracy and folder structure preservation during migration. Make your email transition smoother, safer, and faster with the right approach. Read More:- https://www.esofttools.com/nsf-to-pst-converter.html

How to Optimize Your AWS Environment for Improved Cloud PerformanceThousandEyes

How can one start with crypto wallet development.pptxlaravinson24

Top 10 Client Portal Software Solutions for 2025.docxPortli

Maxon CINEMA 4D 2025 Crack FREE Download LINKyounisnoman75

⭕️➡️ FOR DOWNLOAD LINK : http://drfiles.net/ ⬅️⭕️ Maxon Cinema 4D 2025 is the latest version of the Maxon's 3D software, released in September 2024, and it builds upon previous versions with new tools for procedural modeling and animation, as well as enhancements to particle, Pyro, and rigid body simulations. CG Channel also mentions that Cinema 4D 2025.2, released in April 2025, focuses on spline tools and unified simulation enhancements. Key improvements and features of Cinema 4D 2025 include: Procedural Modeling: New tools and workflows for creating models procedurally, including fabric weave and constellation generators. Procedural Animation: Field Driver tag for procedural animation. Simulation Enhancements: Improved particle, Pyro, and rigid body simulations. Spline Tools: Enhanced spline tools for motion graphics and animation, including spline modifiers from Rocket Lasso now included for all subscribers. Unified Simulation & Particles: Refined physics-based effects and improved particle systems. Boolean System: Modernized boolean system for precise 3D modeling. Particle Node Modifier: New particle node modifier for creating particle scenes. Learning Panel: Intuitive learning panel for new users. Redshift Integration: Maxon now includes access to the full power of Redshift rendering for all new subscriptions. In essence, Cinema 4D 2025 is a major update that provides artists with more powerful tools and workflows for creating 3D content, particularly in the fields of motion graphics, VFX, and visualization.

Microsoft AI Nonprofit Use Cases and Live Demo_2025.04.30.pdfTechSoup

In this webinar we will dive into the essentials of generative AI, address key AI concerns, and demonstrate how nonprofits can benefit from using Microsoft’s AI assistant, Copilot, to achieve their goals. This event series to help nonprofits obtain Copilot skills is made possible by generous support from Microsoft. What You’ll Learn in Part 2: Explore real-world nonprofit use cases and success stories. Participate in live demonstrations and a hands-on activity to see how you can use Microsoft 365 Copilot in your own work!

Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Versionsaimabibi60507

Copy & Past Link👉👉 https://dr-up-community.info/ Pixologic ZBrush, now developed by Maxon, is a premier digital sculpting and painting software renowned for its ability to create highly detailed 3D models. Utilizing a unique "pixol" technology, ZBrush stores depth, lighting, and material information for each point on the screen, allowing artists to sculpt and paint with remarkable precision .

TestMigrationsInPy: A Dataset of Test Migrations from Unittest to Pytest (MSR...Andre Hora

Unittest and pytest are the most popular testing frameworks in Python. Overall, pytest provides some advantages, including simpler assertion, reuse of fixtures, and interoperability. Due to such benefits, multiple projects in the Python ecosystem have migrated from unittest to pytest. To facilitate the migration, pytest can also run unittest tests, thus, the migration can happen gradually over time. However, the migration can be timeconsuming and take a long time to conclude. In this context, projects would benefit from automated solutions to support the migration process. In this paper, we propose TestMigrationsInPy, a dataset of test migrations from unittest to pytest. TestMigrationsInPy contains 923 real-world migrations performed by developers. Future research proposing novel solutions to migrate frameworks in Python can rely on TestMigrationsInPy as a ground truth. Moreover, as TestMigrationsInPy includes information about the migration type (e.g., changes in assertions or fixtures), our dataset enables novel solutions to be verified effectively, for instance, from simpler assertion migrations to more complex fixture migrations. TestMigrationsInPy is publicly available at: https://github.com/altinoalvesjunior/TestMigrationsInPy.

Societal challenges of AI: biases, multilinguism and sustainabilityJordi Cabot

F-Secure Freedome VPN 2025 Crack Plus Activation New Versionsaimabibi60507

FL Studio Producer Edition Crack 2025 Full Versiontahirabibi60507

Secure Test Infrastructure: The Backbone of Trustworthy Software DevelopmentShubham Joshi

Download YouTube By Click 2025 Free Full Activatedsaniamalik72555

Adobe Marketo Engage Champion Deep Dive - SFDC CRM Synch V2 & Usage DashboardsBradBedford3

LEARN SEO AND INCREASE YOUR KNOWLDGE IN SOFTWARE INDUSTRYNidaFarooq10

WinRAR Crack for Windows (100% Working 2025)sh607827

Adobe Master Collection CC Crack Advance Version 2025kashifyounis067

Why Orangescrum Is a Game Changer for Construction Companies in 2025Orangescrum

Scaling GraphRAG: Efficient Knowledge Retrieval for Enterprise AIdanshalev

PDF Reader Pro Crack Latest Version FREE Download 2025mu394968

How to Batch Export Lotus Notes NSF Emails to Outlook PST Easily?steaveroggers

How to Optimize Your AWS Environment for Improved Cloud PerformanceThousandEyes

How can one start with crypto wallet development.pptxlaravinson24

Top 10 Client Portal Software Solutions for 2025.docxPortli

Maxon CINEMA 4D 2025 Crack FREE Download LINKyounisnoman75

Microsoft AI Nonprofit Use Cases and Live Demo_2025.04.30.pdfTechSoup

Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Versionsaimabibi60507

TestMigrationsInPy: A Dataset of Test Migrations from Unittest to Pytest (MSR...Andre Hora

Societal challenges of AI: biases, multilinguism and sustainabilityJordi Cabot

F-Secure Freedome VPN 2025 Crack Plus Activation New Versionsaimabibi60507

Micro-services Battle Scars

3. 4 years of Node.js 50+ projects startups to gorillas 1 user to 1 000 000 every kind team all skill levels nearForm ❤️ micro-services. Richard Rodger @rjrodger

4. What do you think micro-services are made of?

5. You run lots of little processes, on many machines.

6. All services can see All messages … and react to the ones they care about - a useful fiction! Your services communicate using asynchronous messages.

7. Messages are just JSON documents. Patterns are just property-value pairs. info:user, what:login You use pattern-matching to react to the right messages.

8. You get real software components. Finally!

9. •re-usable •which really means: composable •extensible •easy to add functionality •encapsulated and loosely coupled •the implementation does not leak •well-defined interface •but note: this does not mean strict! Here’s what software components should do for you.

10. How do you write micro-services to handle this?

11. Write more micro-services when you need to specialise. Add more specific patterns for more fine-grained functionality. You always add services, never modify. Pattern matching makes this work.

12. You get service composition when you use pattern matching.

13. nodezoo.com - github.com/rjrodger/nodezoo An example system big enough to be interesting.

14.  PILE OF POO U+1F4A9 You can get yourself into trouble with micro-services…

15. You may get a rash of little web servers. This never ends well.

16. Define a schema for the properties of the Chair entity. Make sure you cover all the business cases! Jon Postel: You should be liberal in what you accept, and strict in what you emit.

17. You can never get away from some anti-patterns.

18. You can use any language! What could possibly go wrong?

19. Architecture. The boxes and arrows don’t work anymore. You’ll discover more services than you’ll design.

20. Don’t keep any state in your services. We’ve tried that already with OOP. It doesn’t work. You use micro-services to perform actions. They don’t describe the world.

21. You’ll need practice. Micro-services break lots of rules.

22.  ROCKET U+1F680 You can be awesome with micro-services.

23. You can swap databases mid-project! Or anything else. Infinite Power!

24. Your system will scale.

25. You can actually do continuous deployment! Micro-services are the “unit of deployment”.

26. You can verify new micro-service versions work by running them beside old versions.

27. senecajs.org nearform.com/nscale nodejs.org docker.com You’ll need some tools to make this work.

28. Thanks! Richard Rodger @rjrodger

Micro-services Battle Scars

Recommended

More Related Content

Viewers also liked (10)

Similar to Micro-services Battle Scars (20)

More from Richard Rodger (20)

Recently uploaded (20)

Micro-services Battle Scars