Picture Wall - 27 pics
If All You Have Is a Database, Everything Looks Like a Nail - Scattered Thoughts on Distributed Systems
GitHub - lucasepe/draft: Generate High Level Microservice Architecture diagrams for GraphViz using simple YAML syntax.
Nicolas Grilly sur Twitter : "Only 3 good reasons for using #microservices instead of building a monolith: - You have multiple teams with clear responsibilities: 1 service per team - You use various technologies: 1 service per tech (e.g. Go and JVM) - Your services scale differently (CPU, RAM, disk, network)"
Patrick McKenzie sur Twitter : ""Monoliths versus microservices: Make it a monolith. Done. You won't have sufficient organizational complexity to justify the engineering tax of microservices until you have multiple engineering teams, and plausibly your company never gets there.""
Mario Fusco 🇪🇺 sur Twitter : "Applying the KISS principle also implies doing "boring" stuff instead of blindly following the coolest trends of the moment. Do monoliths unless you don't need microservices for a good reason. Use synchronous code unless you don't need async or reactive for a good reason.… https://t.co/qL0G3wgcmp"
Franck Pachot sur Twitter : "So, today, #monolithic is used as a pejorative word for software which: - link their functions to be executed by one processor without unpredictable latency - are clever enough to share memory among multiple processes - can read/write to same files from multiple nodes 🙄"
Sonia Gupta sur Twitter : "Sometimes I think microservices architecture is just an excuse for developers to build a lot of unnecessary shit. Something tech is really good at doing."
Darren Shepherd sur Twitter : "Microservices are a way to ensure your application has the same level of complexity as your organization."
Clemens Vasters 🇪🇺☁📨 sur Twitter : "The cycle closing with service meshes is quite long. We are back to service registries and compiled RPC proxies and intermediary crosscutting services as with DCE and CORBA now. The eventual recovery from that will again be loosely coupled and async.… https://t.co/REmcWbQNov"
Matt Stine on Twitter: "had another opportunity to do an architecture review for a monolith to microservices migration today...observations to come:"
William Louth on Twitter: "All these software developers who can’t seem to extract/define/create an appropriate model and interface for a bunch of code blocks are somehow going to create well designed microservices API? Right....."
Andrea Francia on Twitter: "The “distribulith” is the architectural style that combines the immobility of monoliths with fragility of microservices. Applied thoroughly, it helps the developer to fill his resumes with the technologies needed to be hired by the next company, while dooming the current one."
DHH on Twitter: "Microservices is not so much a technical pattern as a Keynesian one. Stimulating the economy by requiring three programmers to screw in the lightbulbs that used to take one. I strongly support its use at Big Cos and in downturns 😄👍"
resilience4j/resilience4j: Resilience4j is a fault tolerance library designed for Java8 and functional programming