Martin Baroš
AI/ML & Cloud Architect @Trustsoft
Prague, Czechia
Actions
AI/ML & Cloud Architect from Slovakia, with a strong background in Cloud Engineering and software development, with over 7 years of experience in Cloud technologies. Currently serving at Trustsoft, with previous experience as a Senior Cloud Engineer, AI/ML Engineer and a Lead Back-end Developer.
Links
Area of Expertise
Topics
Your Lambda's New Caller Is a Language Model
Your Lambdas were built for callers you could reason about: an API Gateway with a rate limit, a queue with a batch size. Now one of them decides for itself how often to invoke you, with arguments inferred from a docstring you never treated as production config.
One question becomes two hundred calls, a six-step agent chain compounds into eighteen sequential invocations inside one user request, and idempotency keys stop matching because a model doesn't retry, it re-reasons. This session takes the tool provider's chair: what to harden in functions you already run, how to architect them and more.
Routing AI Work to the Right Serverless Tier
For a decade, "put it on Lambda" was one decision. It's now four - Functions, Managed Instances, MicroVMs, Durable Functions - with different cost curves, different latency profiles and different limits, all sitting behind the same mental model in most people's heads.
One agentic app spans all of them: bursty embeddings, a streaming gateway idling on CPU, isolated code execution, and orchestration waiting on a human. This session maps shape to tier - where the curves cross, what you give up, and when AgentCore or plain Functions wins instead.
You Can Never Delete an Event
You publish the OrderPlaced event. On day one, there is one consumer, and it’s yours. Two years later, there are eleven, owned by four teams, two of which you have never spoken to, and one of which is a third party with a contract. Now change the event.
Event-driven architecture is sold on decoupling, and it delivers - that’s exactly the problem. With an HTTP API, you can see your callers, measure them, deprecate with a header, and find the two who didn’t migrate. On an event bus, your consumers are invisible by design: the property you bought is the property that stops you from changing anything, and nobody mentions that at the point where you’re drawing the boxes. This session covers the part of event-driven architecture that only shows up in year three - what a breaking change actually is when the contract is an event, four versioning strategies and what each one really costs you and more.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top