Bert Jan is CTO at OpenValue and focuses on Java, software architecture, Continuous Delivery and DevOps. Bert Jan is a Java Champion, JavaOne Rock Star speaker, Duke's Choice Award winner and leads NLJUG, the Dutch Java User Group. He loves to share his experience by speaking at conferences, writing for the Dutch Java magazine and helping out Devoxx4Kids with teaching kids how to code. Bert Jan is easily reachable on X at @bjschrijver.
In software design and software architecture, we often face the question: should we build this generic or specific?
Usually, this is not an easy question to answer. The answer depends on a lot of different factors, including future factors you may not be aware of - yet.
In this talk, I’ll share my experiences and thought process as a developer and software architect with choosing between generic and specific solutions. I’ll talk about generic vs specific design & architecture, both on a project level and organization level. We’ll look at sharing code/components between teams, inner source culture, monorepo’s, microservices, lifecycle management of generic components and strategic design as a tool to help decide. After this talk, you’ll have practical insights that can help you to choose between generic and specific solutions yourself.
Short version: In this talk, I'll show how I migrated the backend for the NLJUG conference app (used for J-Fall, J-Spring and more events) from Spring running on Linux virtual machines to Quarkus running as GraalVM native image on AWS lambda.
Long(er) version:
A conference app backend makes the ideal candidate for a serverless architecture: almost no traffic during the year, and peak traffic during conference days.
In this talk, I'll show how I migrated the backend for the NLJUG conference app (used to rate talks for conferences with 1500+ attendees) from a traditional approach with Java and Spring running on Linux VM's to a fully serverless architecture with Quarkus, GraalVM native images, AWS lambda, API gateway and DynamoDB.
I'll talk about (and demo) the Quarkus development experience, migrating code to Quarkus, creating native images and the caveats involved, testing, deploying to AWS with the SAM CLI, monitoring, costs and more.
After this talk, you'll know enough to get started with building and deploying Quarkus native images on AWS Lambda yourself!
The speaker has never seen the deck they are about to present, and is told the subject matter just before the clock starts ticking.
20 slides will auto-advance every 15 seconds.
What could possibly go wrong?
Searching for speaker images...