Design Microservice Architectures the Right Way

Channel:InfoQ · Length:48:29 · Published:2018-10-23 · Views:741433

Watch on YouTube

Summary

Michael Bryzek of Flow gives a QCon London 2018 talk on key decisions for building maintainable microservices. It covers infrastructure, continuous deployment, communication, event streaming and language choice.

Why HN recommends it

HN commenters recommend it for showing the tooling possible when schemas and APIs are treated as code.

There's a great talk that I highly recommend about some of the magic you can do — HN, 2020

Software architecture & design · Cloud, DevOps & reliability

Subtitles (excerpt)

today we're going to talk about designing microservice architectures the right way and I thought to start it'd be helpful to share a personal story that I hope resonates with many of you so the names will be unnamed but it basically goes like this could you please change this URL from phu kham slash latest slash bar to phu kham slash one point five point three slash bar and the answer is sorry that would take weeks we don't have the resources to do that it's just a frigging URL and we have to ask how does that happen and in this particular case this was a URL in a library there are hundreds of services to update many other services have not been updated in a long period of time which means that updating that service means updating its dependencies which just frankly takes time it is actually the reality of the work to do it and incredibly frustrating right I mean super super frustrating when a simple task ends up being complicated or time-consuming in practice and this is where I think great architecture can really help us and we talk about great architecture I think what we're really after is a few key features one is this idea that we can scale development teams develop deliver higher quality

On Hacker News

My main reasons: 1. It's standardized all the implementation for each language is roughly similar and has the same feature sets (middlewares, stubs, retry, hedging, timeouts, deadlines, etc). 2. High performance framework/webserver in "every" language. No more "should I use flask or the built in http server or gunicorn or waitress or..." 3. Tooling can be built around schemas as code. There's a g… — gravypod, 2020-10
Reminds me a lot of this talk: [VIDEO] I think it's a really powerful paradigm. I think an org adopting such patterns widespread leads to some really rad capabilities. GDPR compliance, for example, is really tough in SOA architectures in companies without a ton of engineering capacity, but this sort of data/api introspection could do a lot to change that. Any plans to open source projection for l… — bpicolo, 2021-05
Flow.io (Flow Commerce) | Hoboken, New Jersey | Dublin, Ireland - [LINK] Flow is a next generation solution for cross-border commerce. Backed by Bain Capital Ventures, Flow has built an API-first, turn-key solution that has been transforming how brands localize their site and sell cross-border. Flow integrates into existing e-commerce platforms and provides brands with a high degree of flexibilit… — zobia, 2019-07

Related videos