Good videos, with context.
Design Microservice Architectures the Right Way

Design Microservice Architectures the Right Way

InfoQ
2 HN recommenders · discussed 2019–2021
Open YouTube ↗

About this video

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 it appears in the archive

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

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

gravypod · 2020-10 · strong rec

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 great talk that I highly recommend about some of the magic you can do [0]. 4. Protos are great for serialization and not just over a network! Need to store configs or data in a range of formats (json, prototxt, binary, yaml)? 5. Streaming. It's truely amazing and can dramatically reduce latency if you need to do a lot of collection-of-things or as-soon-as-x processing. 6. Lower resource usage. Encoding/decoding protos is faster then encoding and decoding json. At high throughput that begins to matter. 7. Linting & standards can be defined and enforced programatically [1] 8. Pressures people to document things. You comment your .c or .java code, why not comment your .proto? [0] - [VIDEO] [1] - [LINK]

Read original comment ↗
bpicolo · 2021-05 · rec

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 languages other than Java? edit: I see that typescript and rust are available on github as well

Read original comment ↗
zobia · 2019-07 · reference

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 flexibility over all aspects of the customer experience (local currency pricing, duty & tax calculation, local merchandising), local checkout (local payment methods, local language) and cheap/fast international shipping options resulting in steep growth in international sales. Our dream is to remove borders from global commerce. We are building a point-to-point global eCommerce platform that enables brands to expand internationally. We help brands with everything from catalog management, pricing, currency risk, payment processing, to logistics. The business was founded by Mike Bryzek (co-founder/CTO of e-commerce giant, Gilt Groupe) and Rob (founder/CEO of leader in customer experience, Fizzback). Our approach to software is pretty unique and offers great opportunities to learn. We are a microservices architecture (Scala backends, ReactJS frontends), practice API-first software development, and run continuous delivery (merging a PR deploys the change). You can find more on our approach to software delivery here ( [LINK] ) and on YouTube ( [VIDEO] ) (100k+ views and counting!) Current open roles

Read original comment ↗