Predstavitev orodja za razvoj cloud native rešitev Micronaut

Predavanje je namenjeno predstavitvi orodja Micronaut, ki ga v konzorciju podjetij Micronaut Foundation razvijamo in je namenjen razvoju in testiranju različnih vrst aplikacij kot so cloud-native mikrostoritve, aplikacij, ki jih poganjamo z ukazne vrstice kot tudi velikih monolitnih aplikacij. V ta konzorciju so glavni partnerji ObjectComputing Inc. (za katerega delam jaz), Google, Amazon, Microsoft in pa Oracle Inc., ki je pred letom dni postal inženiring partner. Micronaut odlikuje izredno kratek zagonski čas aplikacije in manjša poraba pomnilniških in procesorskih resursov, kot ostala primerljiva orodja.

Ker je Micronaut orodje, ki v celoti podpira cloud-native principe, so cloud-native lastnosti kot so service discovery ter configuration management kot tudi možnost poganjanja Micronaut aplikacij v okoljih kot sta Google Cloud Run ter AWS Lambda del orodja in so podpre v vseh glavnih cloud okoljih (Amazon Web Services, Google Cloud, Oracle Cloud Infrastructure ter Microsoft Azul). Programski jeziki, ki jih Micronaut podpira so Java, Kotlin ter Groovy, kar omogoča razvijalcem, da uporabijo programski jezik, v katerem se najlažje izražajo. Micronaut ima prav tako vgrajeno podporo za različne sporočilne sisteme (Kafka, RabbitMQ) in podatkovne zbirke (Oracle, Postgres, MongoDB, Redis in drugi) ter v celoti podpira Hibernate ORM ter JPA.

Zaradi hitrega zagona je pisanje testov oziroma TDD (test driven development) pristop k razvoju aplikacij še posebej zanimiv oziroma olajšan saj lahko enostavno testiramo celotno aplikacijo oziroma izvajamo integracijske teste v času, ki smo ga prej porabili za unit teste. Ker Micronaut za pripravo svoje infrastrukture ne uporablja Java Reflection je vsaka Micronaut aplikacija pripravljena za uporabo GraalVM prevajalnika, kar pomeni, da jo enostavno prevedemo v binarno obliko in jo lahko izvajamo brez uporabe JVM (Java Virtual Machine) V predavanje je vključen tudi kratek prikaz razvoja aplikacije z orodjem Micronaut.

Practical introduction to OpenTelemetry tracing

Tracking a request’s flow across different components in distributed systems is essential. With the rise of microservices, their importance has risen to critical levels. Some proprietary tools for tracking have been used already: Jaeger and Zipkin naturally come to mind.

Observability is built on three pillars: logging, metrics, and tracing. OpenTelemetry is a joint effort to bring an open standard to them. Jaeger and Zipkin joined the effort so that they are now OpenTelemetry compatible.

In this talk, I’ll describe the above in more detail and showcase a (simple) use case to demo how you could benefit from OpenTelemetry in your distributed architecture.

Chopping the monolith

Micro services are ubiquitous. However, most companies that implement micro services do not reap their full benefits - at best. At worst, it’s an epic failure.

There are reasons for micro services: independent deployment of business capabilities. However, the unspoken assumption is that you need to deploy all capabilities all the time. My experience has shown me that it’s plain wrong. Some capabilities need frequent deployment, while some are much more stable. In “the past”, we used Rule Engines to allow updating business rules without deployment. While it solved the problem, this approach had issues. Between introducing a Rule Engine and migrating your complete system to micro services, I believe that there’s a middle path, and that this path is Function-as-a-Service.

In this talk, I’ll detail every point I’ve made above, and show how one can use Serverless to pragmatically design a system that allows deploying as often as you need.

Predstavitev orodja za razvoj cloud native rešitev Micronaut

Predavanje je namenjeno predstavitvi orodja Micronaut, ki ga v konzorciju podjetij Micronaut Foundation razvijamo in je namenjen razvoju in testiranju različnih vrst aplikacij kot so cloud-native mikrostoritve, aplikacij, ki jih poganjamo z ukazne vrstice kot tudi velikih monolitnih aplikacij. V ta konzorciju so glavni partnerji ObjectComputing Inc. (za katerega delam jaz), Google, Amazon, Microsoft in pa Oracle Inc., ki je pred letom dni postal inženiring partner. Micronaut odlikuje izredno kratek zagonski čas aplikacije in manjša poraba pomnilniških in procesorskih resursov, kot ostala primerljiva orodja.

Ker je Micronaut orodje, ki v celoti podpira cloud-native principe, so cloud-native lastnosti kot so service discovery ter configuration management kot tudi možnost poganjanja Micronaut aplikacij v okoljih kot sta Google Cloud Run ter AWS Lambda del orodja in so podpre v vseh glavnih cloud okoljih (Amazon Web Services, Google Cloud, Oracle Cloud Infrastructure ter Microsoft Azul). Programski jeziki, ki jih Micronaut podpira so Java, Kotlin ter Groovy, kar omogoča razvijalcem, da uporabijo programski jezik, v katerem se najlažje izražajo. Micronaut ima prav tako vgrajeno podporo za različne sporočilne sisteme (Kafka, RabbitMQ) in podatkovne zbirke (Oracle, Postgres, MongoDB, Redis in drugi) ter v celoti podpira Hibernate ORM ter JPA.

Zaradi hitrega zagona je pisanje testov oziroma TDD (test driven development) pristop k razvoju aplikacij še posebej zanimiv oziroma olajšan saj lahko enostavno testiramo celotno aplikacijo oziroma izvajamo integracijske teste v času, ki smo ga prej porabili za unit teste. Ker Micronaut za pripravo svoje infrastrukture ne uporablja Java Reflection je vsaka Micronaut aplikacija pripravljena za uporabo GraalVM prevajalnika, kar pomeni, da jo enostavno prevedemo v binarno obliko in jo lahko izvajamo brez uporabe JVM (Java Virtual Machine) V predavanje je vključen tudi kratek prikaz razvoja aplikacije z orodjem Micronaut.

Practical introduction to OpenTelemetry tracing

Tracking a request’s flow across different components in distributed systems is essential. With the rise of microservices, their importance has risen to critical levels. Some proprietary tools for tracking have been used already: Jaeger and Zipkin naturally come to mind.

Observability is built on three pillars: logging, metrics, and tracing. OpenTelemetry is a joint effort to bring an open standard to them. Jaeger and Zipkin joined the effort so that they are now OpenTelemetry compatible.

In this talk, I’ll describe the above in more detail and showcase a (simple) use case to demo how you could benefit from OpenTelemetry in your distributed architecture.

Eclipse MicroStream - Ultra-fast Java cloud-native persistence for microservices and serverless apps

Hibernate is the de facto standard persistence framework for traditional Java database applications. Now, Eclipse MicroStream was built to be the Java persistence for containerized microservices and serverless functions. Eclipse MicroStream follows the system prevalence architectural pattern. The engine enables seamlessly storing any Java objects of any size and complexity transaction-save into cloud-native blob stores such as AWS S3 or any other binary storage. ACID transactions are journaled and deltas of the system state are regularly saved to disk. To reduce startup time and run also with a small RAM capacity of under 1 GB, MicroStream provides lazy loading. With Java Streams API, queries are executed in memory in microseconds - way faster than comparable JPA queries. Implementing is simple. There are no requirements for the entity classes, no annotations, interfaces, or superclasses, just POJOs. Additionally, expensive mappings or any data conversions are eliminated. The core benefits are extremely high performance, simple implementation, running trouble-free with stateless microservices, and reduced cloud storage costs.

Under the hood: tricks, hacks and techniques that make Quarkus so enjoyable and fast

When we talk about Quarkus, we generally mention what a great platform it is for micro-services, or web applications, and we show how much effort went into the developer experience and all the fancy things it does to make you more productive and happier. Well, this talk isn’t about that. This talk explains how Quarkus achieves that. This talk will explain the challenges we faced when developing Quarkus and all those times where we pushed the boundaries of what it was possible to do, just to make our user’s lives easier. We will talk about bytecode scanning, indexing, modification, working around Java language and bytecode limitations, generating native code, as well as elegant or hacky techniques employed by Quarkus to solve interesting problems. Come to see how the magic is made: behind the scenes. You may be amazed, or scared, but you’re bound to learn a thing or two ?.

"How I beat The Lady Luck?" - Why software developers need side project(s)?

Most of us as software developers have something called a "Main Job", which we do to earn money, provide for our family, take care of our needs. In many cases, the main job may not be according to our desire and control. So what happens to passion and desire to learn something new? That's where a “Side Project” comes in. A “Side Project” is something you do in addition to your main job to fuel your passion to learn something new. It has several benefits such as: living your passion, learning new skills, potential for growth, boosting your mental health, etc. The goal of this presentation is to show what you can do in four, five evenings and enrich your experience. The idea came while I was watching the Eurovision Song Contest with my friends. I wanted to be ahead by knowing who the favourites and possible winners are. The presentation will answer some questions such as: what was the trigger, how to develop your idea, what is needed to make it happen and finally the conclusion.