u/nodemonstersin r/scala • Recommends
Design Microservice Architectures the Right Way
0:00 / 0:00
#microservices#continuousdelivery#scala
Design Microservice Architectures the Right Way
InfoQ
234K subscribers • 65 videos on Hallway • Conference channel
- Recommended by 3 people: 2 on Hacker News and 1 in engineering communities.
- Presented by Michael Bryzek, co-founder of Flow
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
740K views8 years ago3 recommendations
Software designDistributed systemsMicroservices and monolithsSoftware architectureCI/CD and deployment
Michael Bryzek discusses key decisions for building maintainable microservices, covering continuous deployment, API design, and event streaming.
Download the slides & audio at InfoQ: bit.ly/2ypNF04 Michael Bryzek highlights specific key decisions that very directly impact the quality and maintainability of a microservice architecture, covering infrastructure, continuous deployment, communication, event streaming, language choice and more, all to ensure that teams and systems remain productive and scale. This presentation was recorded at QCon London 2018: bit.ly/2hxsoN1 Interested in Software Architecture? Follow the topic on InfoQ: bit.ly/2NmIOpa #Microservices #ContinuousDeployment # ContinuousDelivery #InfoQ #QCon #QConNewYorkWhy it's here
3 people recommend thisWhat people say. Recommended as a highly practical guide to API-first development, continuous delivery, and microservice architecture design.
gravypodon Hacker News • Recommends
On “Application Load Balancers enables gRPC workloads with end to end HTTP/2 support”
…hings 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 - link to this video 1 - link…
bpicoloon Hacker News • Recommends
On “Smithy: A language for defining services and SDKs”
Reminds me a lot of this talk: link to this 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
u/Ashtar_Squirrelin r/dotnet • Mentions
On “What problem(s) does Blazor solve?”
Yes, code generators, but it's still two generators to maintain. Three sets of skills (Language A, Language B, Code Generation).
Sill I agree, with code generation, you can do a lot and keep consistency. I agree with a lot from this talk about Design Microservice Architectures the Right Way, especially the API consistency, the linting, the code and model generation.
zobiaon Hacker News • Mentions
On “Ask HN: Who is hiring? (July 2019)”
…. 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 ( link to this video ) (100k+ views and counting!) Current open roles…
u/bonsy12in r/scala • Mentions
On “Help in finding a talk about code generation from API spec”
link to this video is that the talk?
u/daveinsurgentin r/softwarearchitecture • Mentions
On “Event schema distribution strategies?”
…er avro, and yes you're right it's somewhat irrelevant to the strategy. We have a single repo called 'schema' that we publish to, and ultimately events \*are\* APIs just the same and so we treat the whole thing with the same level of care as we would changes to any public API.
You may find this talk interesting if you have not already seen it: [video \- we've been doing something quite similar for almost five years now in a fully serverless microservice environment, and in addition to the sort of reaffirming pleasure of hearing someone else describe what you're already doing to you on stage it had some things we had not considered or prioritized or just were a bit different which I alwa…