09:23Announcements across Microsoft SQL at Microsoft Ignite 2026 | Data Exposed
Microsoft Developer
This presentation was recorded at GOTO Copenhagen 2024. #GOTOcon #GOTOcph https://gotocph.com Ian Cooper - A Polyglot Coding Architect at Just Eat @ian_hammond_cooper RESOURCES https://bsky.app/profile/icooper.bsky.social https://hachyderm.io/@ICooper https://twitter.com/ICooper https://www.linkedin.com/in/ian-cooper-2b059b https://github.com/iancooper https://ian-cooper.writeas.com ABSTRACT Since James Lewis and Martin Fowler wrote their paper on the microservice architectural style in 2013, a lot of words have been dedicated to the subject. But many of them propagated misunderstandings of the properties of the architectural style. Mis-associations with the Cloud Native style, and misapprehensions on how to move from monolith to microservices, meant that the architectures that emerged often bear little resemblance to the original idea; most are just distributed monoliths. Unsurprisingly these architectures are painful and costly to own. Ten years later, the resulting failure to realise the benefits promised by microservices, or a misunderstanding of what they were, has led to a backlash against microservices; now the prevalent wisdom calls for a "return to the monolith," and posters on Reddit have begun to speak of "Death by a Thousand Microservices." This talk looks at the key misunderstandings around microservices: the problems that microservices were intended to solve; "what does micro mean?"; how to achieve independent deployability; how to avoid anti-patterns like
Published 2025-02-28 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.
09:23Microsoft Developer
05:34
02:05
02:17
10:51SyntaxPilot
08:20
04:59IIMTRobot
Allow Google Analytics to measure visits. Your history stays in your browser. Privacy details