Meta tags:

Headings (most frequently used words):

microservices, patterns, architecture, microservice, service, context, about, need, help, your, consulting, learn, the, pattern, server, side, discovery, problem, forces, solution, examples, resulting, related, io, modernizing, 2nd, edition, ask, chris, premium, content, workshops, remote, session, assess, get, book, example, applications, virtual, bootcamp, distributed, data, in, how, to, create, template, and, chassis, build, services, eventuate, platform,

Text of the page (most frequently used words):
the (48), and (25), service (25), microservices (20), architecture (15), for (14), #microservice (12), chris (11), #discovery (11), router (11), your (10), that (10), patterns (9), client (9), side (8), pattern (7), help (7), services (7), learn (7), load (7), instances (7), example (6), use (5), distributed (5), how (5), more (5), about (5), another (5), request (5), server (5), number (5), elb (5), using (4), makes (4), data (4), you (4), consulting (4), can (4), are (4), api (4), richardson (4), need (4), modernization (4), must (4), http (4), instance (4), dynamically (4), group (3), eventuate (3), code (3), virtual (3), now (3), book (3), application (3), question (3), avoid (3), such (3), workshops (3), premium (3), available (3), this (3), modern (3), system (3), with (3), communication (3), might (3), registry (3), when (3), based (3), also (3), some (3), balancer (3), proxy (3), traffic (3), ec2 (3), call (3), location (3), locations (3), one (3), enable (2), saga (2), cqrs (2), implement (2), queries (2), management (2), platform (2), create (2), engage (2), teaches (2), template (2), chassis (2), multiple (2), video (2), ask (2), bootcamp (2), want (2), see (2), applications (2), get (2), assess (2), architect (2), session (2), design (2), problem (2), monolith (2), organization (2), adopt (2), got (2), related (2), remote (2), will (2), content (2), organizations (2), through (2), software (2), edition (2), legacy (2), systems (2), supported (2), kong (2), inter (2), solution (2), invoke (2), thrift (2), etc (2), unless (2), tcp (2), part (2), cloud (2), has (2), following (2), environments (2), aws (2), elastic (2), does (2), context (2), run (2), each (2), host (2), functions (2), port (2), assigned (2), forwards (2), requests (2), which (2), set (2), balance (2), either (2), via (2), runs (2), well (2), known (2), their (2), changes (2), rest (2), mechanism (2), typically (2), please, javascript, view, comments, powered, disqus, join, google, ready, start, latest, startup, easy, manage, transactions, tackle, challenges, adoption, roadmap, define, build, email, marketing, trust, signup, newsletter, take, look, develop, manning, liveproject, regular, price, 395, person, but, coupon, offefkcw, sign, valid, until, sept, 30th, 2025, there, deeper, discounts, buying, seats, consists, lectures, labs, weekly, anything, conference, repeated, timezones, covers, key, including, composition, open, enrollment, check, out, read, offers, numerous, other, resources, learning, identify, what, needs, improved, conduct, review, consider, signing, two, hour, highly, focussed, facing, tricky, know, migrate, wondering, whether, should, specific, pitfalls, adopting, essential, topics, decomposition, refactor, architects, developers, effectively, comprehensive, paid, subscribers, training, engagements, improve, agility, competitiveness, better, fill, write, blog, post, answers, form, very, excited, announce, meap, second, 2nd, trap, creating, new, same, old, problems, contact, discuss, goals, modernizing, created, creator, original, cloudfoundry, com, author, advises, building, becoming, copyright, 2026, all, rights, reserved, alternative, circuit, breaker, uses, network, hops, required, than, support, necessary, protocols, grpc, environment, component, installed, configured, replicated, availability, capacity, drawbacks, provide, functionality, compared, simpler, since, not, have, deal, instead, simply, benefits, resulting, clustering, solutions, order, access, connects, local, then, running, somewhere, cluster, marathon, kubernetes, opens, connections, balances, amongst, external, from, internet, deployed, vpc, internal, registered, explicitly, automatically, auto, scaling, examples, diagram, shows, structure, making, built, into, vary, autoscaling, adjusts, machines, containers, usually, dynamic, addresses, exposes, particular, forces, gateway, discover, consequently, enables, clients, make, changing, ephemeral, monolithic, language, level, method, procedure, calls, traditional, deployment, fixed, hosts, ports, easily, rpc, however, virtualized, containerized, where, testing, refactoring, presentations, articles,

Text of the page (random words):
pattern server side service discovery microservice architecture supported by kong patterns articles presentations adopt refactoring testing modernization help about pattern server side service discovery pattern inter service communication service discovery context services typically need to call one another in a monolithic application services invoke one another through language level method or procedure calls in a traditional distributed system deployment services run at fixed well known locations hosts and ports and so can easily call one another using http rest or some rpc mechanism however a modern microservice based application typically runs in a virtualized or containerized environments where the number of instances of a service and their locations changes dynamically consequently you must implement a mechanism for that enables the clients of service to make requests to a dynamically changing set of ephemeral service instances problem how does the client of a service the api gateway or another service discover the location of a service instance forces each instance of a service exposes a remote api such as http rest or thrift etc at a particular location host and port the number of services instances and their locations changes dynamically virtual machines and containers are usually assigned dynamic ip addresses the number of services instances might vary dynamically for example an ec2 autoscaling group adjusts the number of instances based on load solution when making a request to a service the client makes a request via a router a k a load balancer that runs at a well known location the router queries a service registry which might be built into the router and forwards the request to an available service instance the following diagram shows the structure of this pattern examples an aws elastic load balancer elb is an example of a server side discovery router a client makes http s requests or opens tcp connections to the elb which load balances the traffic amongst a set of ec2 instances an elb can load balance either external traffic from the internet or when deployed in a vpc load balance internal traffic an elb also functions as a service registry ec2 instances are registered with the elb either explicitly via an api call or automatically as part of an auto scaling group some clustering solutions such as kubernetes and marathon run a proxy on each host that functions as a server side discovery router in order to access a service a client connects to the local proxy using the port assigned to that service the proxy then forwards the request to a service instance running somewhere in the cluster resulting context server side service discovery has a number of benefits compared to client side discovery the client code is simpler since it does not have to deal with discovery instead a client simply makes a request to the router some cloud environments provide this functionality e g aws elastic load balancer it also has the following drawbacks unless it s part of the cloud environment the router must is another system component that must be installed and configured it will also need to be replicated for availability and capacity the router must support the necessary communication protocols e g http grpc thrift etc unless it is tcp based router more network hops are required than when using client side discovery related patterns a router uses service registry a router might use a circuit breaker to invoke services client side discovery is an alternative solution pattern inter service communication service discovery modernization help copyright 2026 chris richardson all rights reserved supported by kong about microservices io microservices io is created by chris richardson software architect creator of the original cloudfoundry com and author of microservices patterns chris advises organizations on modernization architecture and building systems that avoid becoming modern legacy systems need help modernizing your architecture avoid the trap of creating a modern legacy system a new architecture with the same old problems contact me to discuss your modernization goals get help microservices patterns 2nd edition i am very excited to announce that the meap for the second edition of my book microservices patterns is now available learn more ask chris got a question about microservices fill in this form if i can i ll write a blog post that answers your question need help i help organizations improve agility and competitiveness through better software architecture learn more about my consulting engagements and training workshops premium content premium content now available for paid subscribers at premium microservices io microservices workshops chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively avoid the pitfalls of adopting microservices and learn essential topics such as service decomposition and design and how to refactor a monolith to microservices learn more remote consulting session got a specific microservice architecture related question for example wondering whether your organization should adopt microservices want to know how to migrate your monolith to microservices facing a tricky microservice architecture design problem consider signing up for a two hour highly focussed consulting session assess your architecture assess your application s microservice architecture and identify what needs to be improved engage chris to conduct an architect review learn about microservices chris offers numerous other resources for learning the microservice architecture get the book microservices patterns read chris richardson s book example microservices applications want to see an example check out chris richardson s example applications see code virtual bootcamp distributed data patterns in a microservice architecture my virtual bootcamp distributed data patterns in a microservice architecture is now open for enrollment it covers the key distributed data management patterns including saga api composition and cqrs it consists of video lectures code labs and a weekly ask me anything video conference repeated in multiple timezones the regular price is 395 person but use coupon offefkcw to sign up for 95 valid until sept 30th 2025 there are deeper discounts for buying multiple seats learn more learn how to create a service template and microservice chassis take a look at my manning liveproject that teaches you how to develop a service template and microservice chassis signup for the newsletter for email marketing you can trust build microservices ready to start using the microservice architecture consulting services engage chris to create a microservices adoption roadmap and help you define your microservice architecture the eventuate platform use the eventuate io platform to tackle distributed data management challenges in your microservices architecture eventuate is chris s latest startup it makes it easy to use the saga pattern to manage transactions and the cqrs pattern to implement queries join the microservices google group please enable javascript to view the comments powered by disqus