
De quoi s'agit-il
[formerly London μServices (Microservices) User Group]
The Architectural Monolith’s days are numbered. As companies are becoming more and more agile, and see how they can now adapt in order to innovate and compete faster than their competition, software development teams are being forced to maintain and evolve large, monolithic applications at a pace of change that those architectures were never meant to withstand, let alone embrace!
Microservices are a new approach to architecting applications. They are simple, single-purpose, lightweight architectural components that enable you to deliver software faster. The microservice architectural approach also aims to lead to software that thrives on change while at the same time being secure, performant, and stable.
This meet up is for people interested in architecting, designing, deploying and maintaining micro service based software architectures.
If you want to advertise jobs to the group, read our policy here
Interested in speaking? See how we can help and how it works here
Got a talk? Send it to us here
Événements à venir (3)
Tout voir- London Microservices Meetup - Q2 2025Civo Tech Junction, London
~~~ Agenda ~~~~
18:00 Venue opens
Drinks, pizza, and networking.
18:45 First speaker
19:15 Second Speaker
Q&A and networking until close at 20:30
~~~Speakers~~~1st Speaker
David Denton - Founder at Clockwork and Co-creator of http4K
Functional Intelligence: Agents, MCP And The End Of The Web (?)
This talk touches on a future where autonomous systems, powered by standardised protocols, transform how we interact with digital services and fundamentally reshape the human web experience. Instead of humans adapting to clunky UIs and processes, intelligent agents handle these tasks by directly communicating with each other.
2nd Speaker
Ian Cooper - Senior Principal Engineer - Just Eat
Microservices: Where Did It All Go Wrong?
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 a distributed monolith. It will also explain the problems that a monolith can't solve that cause us to choose microservices.