Tuesday, April 27, 2021
Smart devices form the bedrock of our connected world, and yet they can be a daunting place to get started. Building practical devices requires a multi-disciplinary set of skills and basic knowledge that may seem like an arcane art, but with a proper grounding in fundamentals you can build prototype smart devices with ease. In this session participants will be given a crash course in Electronics and Electrical Engineering concepts that are the foundational knowledge of all smart devices. After the sessions, participants will be able to apply the concepts to building their own prototype smart devices, and expand on those skills with additional projects that they can build.
Harnessing the unique behavior of quantum physics and applying it to computing, quantum computers introduce new concepts to traditional programming methods such as superposition, entanglement, and quantum interference.
Microsoft, having a clear mindset towards the coming quantum era, is partnering with quantum hardware companies to provide developers with cloud access to quantum hardware.
Leveraging the Azure Quantum platform and the Q# language, developers are now able to explore quantum algorithms and run their quantum programs on different types of quantum hardware.
In this session, we will explore Azure Quantum’s capabilities and run a Q# quantum application on a real quantum computer.
Jetpack Compose is changing how UI is being built on Android. This new toolkit is replacing the now 10-year-old, somewhat tedious View system with a declarative, functional approach, and promises to simplify and speed up UI development.
This is happening at the same time as Flutter continuously gaining popularity, and iOS getting its own declarative UI APIs with SwiftUI.
This session explains what Jetpack Compose is, and then shows a quick example of interesting UI with it, based on this blog post https://medium.com/google-developer-experts/compose-oclock-50c778a6360
Not too long ago, a reactive variant of the JDBC API was released, known as Reactive Relational Database Connectivity (R2DBC). While R2DBC started as an experiment to enable integration of SQL databases into systems that use reactive programming models, it now specifies a robust specification that can be implemented to manage data in a fully-reactive and completely non-blocking fashion.
In this session, we’ll briefly go over the fundamentals that make R2DBC so powerful. We'll keep light on the slides so that we can jump directly into application code to get a first-hand look at the recently released R2DBC client from MariaDB. From there we'll examine how you can take advantage of crucial concepts, like event-driven behavior and backpressure, that enable fully-reactive, non-blocking interactions with a relational database.
With Mobile on track to contribute to 72% of global e-commerce sales by 2021, Apps are playing a pivotal role for both user acquisition but also retention and engagement. Come learn how to make the most out of your Mobile App by leveraging Mobile Apps Promotion solutions and strategies. The session will cover the role of Apps within the E-Commerce industry, best practices and success stories from some of our partners as well as product roadmap
A CI/CD pipeline seems straightforward to implement and maintain. Yet it can often quickly become a tedious time sink and a source of universal frustration on many teams. From flaky builds, to long running builds, to flaky long running builds, the sources of frustration are endless. With the goal to ship more and faster as well as to compete in an ever changing industry, we can (and must) do better.
This talk will cover best practices for performance, stability, security, and maintainability of CI/CD pipelines, each supported with practical examples and counterexamples.
Kafka is great, but it's not well suited for event sourcing.
For streaming events Kafka is a great solution which is scalable and easy to use. But for event sourcing it's not a perfect fit. One of the things we can't get from Kafka is quickly getting all items with the same id. Which is something event stored as made for. This means it's not easy to quickly rehydrate an aggregate.
In an event sourcing architecture often CQRS is applies. To easily handle queries, some intelligent message distribution is needed, which is also something which is not available with the Kafka api.
I will explore these problems and offer some solutions by building a few things onto Kafka instead of sending and receiving the messages directly from Kafka.
This talk is the perfect opportunity for you to see where Cloud Native PostgreSQL, developed by EDB, is currently standing and how it can be integrated in your Kubernetes and OpenShift Container Platform workloads.
Cloud Native PostgreSQL is built on solid concepts and principles such as immutable infrastructure, declarative configuration and application containers, making it also ideal to use in your CI/CD pipelines as part of the applications’ E2E tests.
Join me to discover how our operators adapt to public/private/hybrid environments, how core features such as self-healing, high-availability, scalability and updates work, and – last but not least – what our DevSecOps culture and processes have produced in the area of security.
React server-side rendering (SSR) is a useful optimization feature that helps to boost initial website rendering. However, this optimization comes with a duplicated content trade-off. Partial hydration can reduce that duplication (i.e, optimize the optimization). In this session, Erzhan will share examples of partial hydration that attendees can apply to real world challenges.
At Jobiqo we are building flexible job board software and smart matching technology to enable media brands and organizations to engage talent with job sites. Until recently we were relying solely on managed VPS. In this session, I will talk about the process we undertook while migrating to the cloud.
At the end of this session, attendees will be able to list the pros and cons between managed VPS and cloud hosting. They will also be able to compare different cloud providers and they will be able to evaluate the performance of their cloud.
Security and development teams might not have a lot in common, but there's always a collective sigh of relief when a difficult compliance audit ends. Auditors for SOC 2, ISO 27001 — or really, any framework — will inevitably pull your developers into providing evidence, explaining vague processes, and correcting identified issues. If both teams don't start following best practices well before the audit begins, it sidetracks roadmaps and hurts your ability to deliver on business-critical projects.
So what can development leads do now to minimize disruption later? What changes can your team start already, and what items should you be expecting from your security colleagues? I'll aim to answer both these questions, pulling from 8+ years of experience in leading security teams through compliance audits across a variety of business sizes and industries.
Monolithic applications have been shunned for years now, and micro-services is one of the architectures trying to replace them.
Micro-services suffer from two central problems: 1) they easily become an unmanageable soup of individually versioned components that are hard to manage and continually version, and 2) the paradigm does not really deal with user interfaces.
Micro-GUIs try to resolve the second issue, but the technology is still in the infancy.
Instead, we propose to use micro-applications. It is individual applications that work together to achieve a single goal. Micro-applications are size-wise closer to micro-services, but are self-contained in the sense that they come with data-layer and user-interface (as applicable), reducing the pain of tracing a function point between many different micro-services and allowing internal unpublished interfaces (e.g., keeping services used solely for the GUI private), reducing problem 1, and explicitly splits up the user-interface into blocks, handling problem 2.
Micro-applications allow each application to use its own paradigms and frameworks, allowing freedom in selecting not only technologies but even suppliers, yet tie everything together using a robust single-sign on solution, presenting a single experience to the end-user.
In this talk, we present the architecture in more detail and outline some of our experiences with using the paradigm at multiple customers, as well as a driving architecture for modernization of existing applications and entire landscapes.
The talk is not technical and presents all prerequisites; it is an advantage but not a prerequisite to have felt the pain of altering a 5 years untouched monolith or having to do a wide-sweeping change in a micro-service landscape.
OPEN TALK: Do Not Download Your PDF: A Story of Digital Document Usability and Security in Your ApplicationJoin on Hopin
The usage of digital documents within an app affects basically every industry and use-case and now more than ever. Have you ever looked into incorporating documents into your app? There’s a lot to consider. And what about digital security? When it comes to thinking about the document lifecycle within an app, there are several things to think about:
- The in-app experience when working with multiple documents
- Integrating a viewer inside of the app beyond any built-in viewers
- Providing consistent behavior across multiple browsers
- Providing customized UI for annotating PDFs, images, MS Office documents and videos
- Improving your search across multiple documents beyond just title and metadata
As developers, we can remember the time when Nagios was state-of-the-art technology. We hated looking at all the numbers that seemed disconnected from our reality. The world has changed though, and Observability provides us with a new swiss army-knife in our toolbox. Used correctly it helps to improve reliability, brings additional focus on what matters, the business logic, and offers aid in case of problems or failures. Especially in time-critical situations, a distributed system with many service dependencies can be hard to analyze.
This session you will learn how to use Observability to assist developers instead of distract them.
Since 2011 voice assistants have been entering our lives little by little. It wasn't until 2014 that Amazon created the Echo devices with its built-in assistant, Alexa. In 2018 they give us the opportunity for anyone to add functionality through skills, it means to be able to create voice-based applications for the first time.
What are we going to talk about?
In this talk, a totally pioneering architecture in this type of application will be taught: How to deploy an Alexa Skill in Kubernetes environments. From local development with Kind and DevSpace, through the design of a Helm chart of Alexa Skill itself together with the non-relational database MongoDB, to automatic deployment in AKS with Terraform.
What does it bring to the attendees?
The main goal of this talk is, in addition to learning how to develop an Alexa Skill, to teach attendees the different ways to develop and deploy an Alexa Skill. We will investigate all the different types of deployments supported for these voice applications.
Who will be interested on it?
1. Tech leads nuevas arquitecturas están naciendo a partir de la aparición de estas aplicaciones y plataformas. Es una buena oportunidad para aprender sobre este nuevo enfoque.
2. Product managers puede ser una buena oportunidad para poder detectar nuevas funcionalidades/interacciones de un producto.
3. Engineers si eres un amante de las nuevas tecnologías esta es tu charla!
Keywords: Voice, Alexa, Voice Apps, Azure, Kubernetes, Helm, Docker, AKS, Terraform, Voice First, AI.
Shifting Application Security Left and into the hands of developers has been a topic of discussion, but remains just that, a discussion. Legacy solutions in the market are not built from the ground up to enable this and achieve DevSecOps. In this session we will discuss the key features that your AppSec testing tools need to enable shift left, or shift everywhere, to empower developers to detect, prioritize and remediate security issues EARLY, as part of your agile development and unit testing processes, without slowing down DevOps. The talk will include specific examples from leading organizations that have deployed these solutions, the business impact they have achieved and the steps you can take to achieve the same, across your applications and APIs
Code and data go together like tomato and basil; not many applications work without moving data in some way. As our applications modernise and evolve to become more event-driven, the requirements for data are changing. In this session we will explore Apache Kafka, a data streaming platform, to enable reliable real-time data integration for your applications.
We will look at the types of problems that Kafka is best at solving, and show how to use it in your own applications. Whether you have a new application or are looking to upgrade an existing one, this session includes advice on adding Kafka using the Python libraries and includes code examples (with bonus discussion of pizza toppings) to use.
With Kafka in place, many things are possible so this session also introduces Kafka Connect, a selection of pre-built connectors that you can use to route events between systems and integrate with other tools. This session is recommended for engineers and architects whose applications are ready for next-level data abilities.
Wednesday, April 28, 2021
For a microservices architecture to be succesful it is crucial to have the right boundaries between the microservices. But where are the right boundaries? I would like to present a tool that helps us answer this question.
Domain Storytelling (www.domainstorytelling.org) means that we let our users tell us stories about their work. While listening, we record the stories using a pictographic language. The experts can immediately see if we understand their story. After very few stories, we understand the language of our users and find different areas of the domain. Each of these areas (called a subdomain) is a good candicate to become a microservice in our architecture.
In this talk I show how to find subdomains and which heuristics can help us.
Scaling is hard.
Decentralized architectures are complicated.
So how do we scale decentralized architectures? How should we improve upon existing protocols to allow them to handle a large number of transactions, of users, while maintaining a certain level of decentralization?
We’ll try to get some answers to these questions by first looking at what we’re doing most of the time in centralized architectures, and trying to see if it fits the specifics of decentralized architectures. Then we’ll take a look at some of the options chosen by the most populars public blockchain protocols.
Microservices running in Kubernetes and containerized environments are complex and hard to monitor and troubleshoot. Join us as we discuss the growth in the adoption of Kubernetes and containers and the challenges that they have presented us all, focusing on why standard metrics and logs by themselves are leaving gaps in your observability strategy.
It is not feasible to run an observability infrastructure that is the same size as your production infrastructure. Past a certain scale, the cost to collect, process, and save every log entry, every event, and every trace that your systems generate dramatically outweigh the benefits. If your SLO is 99.95%, then you'll be naively collecting 2,000 times as much data about requests that satisfied your SLI as those that burnt error budget. The question is, how to scale back the flood of data without losing the crucial information your engineering team needs to troubleshoot and understand your system's production behaviors?
Statistics can come to our rescue, enabling us to gather accurate, specific, and error-bounded data on our services' top-level performance and inner workings. This talk advocates a three-R approach to data retention: Reducing junk data, statistically Reusing data points as samples, and Recycling data into counters. We can keep the context of the anomalous data flows and cases in our supported services while not allowing the volume of ordinary data to drown it out.
The future of work has arrived. As product development teams have shifted to working remotely, we’ve had to adjust our processes, communication, and culture. Join Lucidspark to learn how to effectively drive collaboration across distributed teams both now and going forward.