Thank you all for the submission of the topic suggestions. We will announce the schedule soon!
ServerlessDays Warsaw is a developer-oriented conference about serverless technologies.
We believe that technology is a booster for innovation and one of main goals is to shorten a time-to-market. During the sessions speakers share their experience and lessons from real-world projects.
ServerlessDays Warsaw is part of ServerlessDays (formerly JeffConf), a global series of events around the world fostering communities around serverless technologies.
We follow and enforce the Serverless Days Code of Conduct.
The serverless ecosystem has evolved quickly since 2014, from simple event-driven FaaS to a strategic mindset that allows you to build cloud-native applications without thinking about servers. In this keynote, Alex goes through a bit of history to highlight how much has changed, what challenges have been addressed by the community, and which patterns and anti-patterns have emerged so far.
Over the last several years, serverless has gained a tremendous amount of traction among organizations large and small. From the scrappy, one-person startup, to the Fortune 500 enterprise, serverless has changed the way developers are building, deploying, and maintaining their applications. However, the rapid speed of that change has left most of them with a patchwork of tools, frameworks, and practices. At best, this is suboptimal, and at worst, it's completely unsustainable. In this talk, we'll look at how organizations are integrating serverless into their workflows and discuss where improvements can be made to tooling, CI/CD, and other processes to optimize developer productivity and dramatically reduce time-to-value (TTV) and total cost of ownership (TCO).
Serverless environments and functions are protected at the edge of the cloud. However, there is no application protection inside the environment. Malicious code injected at the code production stage can spread freely. The use of one of the vulnerabilities also allows an attacker to penetrate into the environment from the outside and run commands operating in the operating system, execute a script or action in the file system. A demo session will show how you can secure such applications and environments.
Serverless functions have been designed from the start for simplicity, providing a managed runtime to execute your code. But code can include different kinds of dependencies, such as libraries, machine learning models, or graphical assets such as fonts. To help you with these use cases, AWS Lambda now supports container images as a packaging format. Let’s see how this works, when to use it, and how to build container images that work with both functions and traditional container environments.
In recent years the amount of data generated by brands increased dramatically, thanks to affordable storage costs and faster internet connections. In this article, we explore the advantages serverless technologies offer when dealing with a large amount of data and the common pitfalls of these architectures. We are going to outline tips everyone should figure out before starting your next big data project At Neosperience, building our SaaS cloud on AWS, we managed to leverage a number of AWS services. This talk is a deep dive into the choices we made and the reason behind them that made us evolve a standard pipeline with API Gateway + Lambda + DynamoDB into an architecture, able to process hundreds of events per second. In this journey, we’ll discover some unexpected be.
Serverless platforms are built for throughput, not for latency. One of the key risks, and most common complaints when moving to hosted function code services, is that it could make request processing slower. Gojko shows five important architectural ideas to make request processing lightning fast with serverless deployments, based on the author's experience building a document collaboration platform deployed on AWS Lambda since 2016. You will learn how to make your applications better for users, and how to save a lot of money on operational costs.
The Azure Functions seem easy to use but what if our business scenario cannot be implemented using one of the "default" triggers or bindings? "Extension" is the keyword in this case! In this session, we see how to enhance our functions with custom triggers and custom bindings to make the most of the power of Serverless.
Since re: Invent 2020 there are at least three distinct serverless solutions capable of scheduling, monitoring, operating, and running workflows made of sequences of various actions. Such services, called orchestrators, are often playing a crucial role in various applications, especially in machine learning systems (and are also tightly bound to the recent buzzword in the club - MLOps). In this talk we are going to revise why would we even need to orchestrate workflows, scout out available solutions in AWS (CodePipeline, SageMaker Pipelines, Step Functions), walk through the basics of each service, point out their pros and cons, and finally explain when and why should we choose one service over another.
Building applications with serverless technologies changes the developer workflow. A good workflow allows developers to test and iterate on business logic quickly. It enables them to check that business logic runs correctly alongside the managed services that make up an application. This session demonstrates how to use a cloud development environment to enhance your serverless developer workflow. Learn how to speed up your inner loop and build serverless applications from within your local IDE. After this session, you will understand how to solve common development challenges such as “How do I develop locally?”, “How do I test?”, and “Should I mock AWS services?” when building serverless applications.
The serverless approach and related technologies have been with us for some time. Cloud providers keep releasing new services based on this philosophy. Many of them have already fully matured. On the other hand, serverless is often a fashionable slogan that is interpreted differently by many people. During the presentation, I will share my experience in this field. It is backed up by building and maintaining services that have been working in production for several years. I will talk about the path that serverless applications have gone through - from (seemingly) good architecture design to conclusions drawn and evolution through its ruthless verification in a live production environment. Based on my experience, I would also like to share my thoughts on appropriate and unsuccessful use cases of serverless architecture and things to watch out for when implementing such solutions.