This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
We had multiple types and sources of identity tokens, each requiring special handling, the logic for which was replicated in various systems. Critical identity data was being propagated throughout the server ecosystem in an inconsistent fashion. We would need to process authentication tokens (and protocols) further upstream.
In particular, he talked about the misattribution potential in a complex microservicearchitecture where often intermediary results are cached. link] Dropbox Slides The last talk of the event was a systemarchitecture introduction by Dropbox’s Tsahi Glik.
In particular, he talked about the misattribution potential in a complex microservicearchitecture where often intermediary results are cached. link] Dropbox Slides The last talk of the event was a systemarchitecture introduction by Dropbox’s Tsahi Glik.
How do I upgrade or evolve microservices? Which teams are going to run my system? With event-first design, the data becomes the API which, like any production system, needs to support change and evolution (i.e., In the context of a payment system, you might need to drain the current set of payments for a topology change.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content