DevDays Europe 2021
— CONFIRMED TALKS —
Animations are fantastic.
They make our apps feel interactive, increase engagement, and make our designers happy. But until recently, animations were a real pain point, which made it hard to deliver good looking animations, especially if we had a tight deadline.
September 2019 marked the release of .NET Core 3 and December 2019 marked the release of .NET Core 3.1. In this session, we will talk about, including a lot of demo material, what is new in the latest version of .NET Core and what the future will bring for the .NET platform in general.
In the last decades a web server environment has evolved, starting from physical servers, going through virtual machines and containers until most recent serverless computing. With many obvious benefits of serverless computing, some drawbacks came too, including security issues.
Following the in-depth research on AWS security, Pawel dug into serverless computing with some good results.
Everybody knows that we need a cache, but where exactly to place it? Inside your application or as a layer in front of it? In the container or outside the container? In the era of Cloud Native and Microservices these questions get even more complicated. In this session Rafal will present different architectural patterns for distributed caching: Embedded, Client-Server, (Kubernetes) Sidecar, and Reverse HTTP Proxy Caching.
While “software is eating the world”, those who are able to best manage the huge mass of data will emerge out on the top.
The batch processing model has been faithfully serving us for decades. However, it might have reached the end of its usefulness for all but some very specific use-cases. As the pace of businesses increases, most of the time, decision makers prefer slightly wrong data sooner, than 100% accurate data later.
This session mixes many of the lesson learned in years while writing distributed software. First is “design for failures”, to be sure our code will never generates inconsistencies. Second is “stateless (almost) everywhere”, to be sure our compute power can be built in minutes. Third is “performance”, which has to be considered a feature itself while it is often a competitive gap between you and others. In this session we approach the “simple” problem of reducing the computation time of a CPU intensive application, using C#, Queues, Azure Batch and a bit of shell scripting.
Developers love the idea of having safety nets when they work. The feeling that a stable framework, backed by top software companies and supported by community developers, will ensure they can’t go wrong. There is one excellent framework everybody forgets: the web browser.
Using modern web standards, we can add new features/powers into the browser in a snap. Is this too good to be true?
More talks are yet to come!