Abdel Sghiouar is a senior Cloud Developer Advocate at @Google Cloud. A co-host of the Kubernetes Podcast by Google and a CNCF Ambassador. His focused areas are GKE/Kubernetes, Service Mesh, and Serverless. Abdel started his career in data centers and infrastructure in Morocco, where he is originally from, before moving to Google's largest EU data center in Belgium. Then, in Sweden, he joined Google Cloud Professional Services. He spent five years working with Google Cloud customers on architecting and designing large-scale distributed systems before turning to advocacy and community work.
The most secure server is one that is disconnected from the Internet and unplugged. And the most convenient environment for devs is where they have admin access to production and the freedom to do what they want. Sometimes it feels hard to reconcile these two ideals, allowing devs to be free to use whatever dependencies they want while making sure their setup and software are as secure as possible. Hence the term - Software Supply Chain Security, which looks at securing the entire process of getting software from devs to production.
Let's look at a real-world scenario of a cloud-native fintech platform on GKE. The vision? A robust, flexible, and secure foundation that supports SOC2-compliant deployments and empowers developers to be as productive as possible, contrary to the typical for the financial sector blown-out processes and approval chases.
This solution is powered by Google Kubernetes Engine (GKE) and the cloud's niftiest security tools from the Secure Supply Chain toolkit.
Applications typically run better on serverless platforms if they start fast, with instant peak performance and lower CPU/memory consumption. You’ll save on costs if the application needs less time and resources to run on, handle more requests with less CPU/memory and achieve better performance.
We love to use Java for its stability, performance and portability, however we all know that Java and its various web frameworks aren't known for starting fast or not using a lot of resources.
Startup is just the beginning, as serverless applications in the modern enterprise need to be optimized for peak performance and high throughput during their entire execution lifecycle.
Can we achieve it? Don’t worry, we’ll start exploring methodically how this all changes with five technologies geared towards improving Java app runtime efficiency in serverless environments.
- Class Data Sharing (CDS)
- Ahead-of-time-compilation (AOT)
- Native Java Images, with GraalVM
- JVM Checkpoint and Restore, with Project CRaC
- Upcoming OpenJDK runtime efficiency project, Project Leyden
This session leaves you with practical advice you can directly apply in your serverless applications and a full, detailed codebase!
When the business wants to speed up because there is a lot of work and/or (legal) deadlines coming up, a natural response is to expand the workforce. While it's understood that a Scrum team has an optimal size, the alternative of adding more teams brings its own challenges.
This talk will discuss the lessons learned with 3 teams on a single complex project. It will also explain the analogy that you can't make a baby in 1 month with 9 women, highlighting the limitations of adding more teams. It will also explore the benefits you can expect and what it takes to make it work.
This talk will go into the social aspect and technical aids that can help, at the end, you should have a good idea of the benefits and the hidden costs of having multiple teams work on the same project. Even if you are not working with multiple teams then this talk can still improve the collaboration in your team.
Searching for speaker images...