Erik Lindblom's Ramblings

So, this idea is a slight continuation on from my notes of how to get a stream out of JDBC using the Simpleflatmapper library. The goal here is to make it so I can send a stream of objects out with JAX-RS (Jersey). This makes it possible to have lazy evaluation of a stream of data from a database that gets pushed up to the browser as soon as it comes off the database.

When I was a C# developer, I adored the different Micro-ORMs that were available. Massive was one of the first ones I heard about and used. The idea that I could just write straight SQL and get objects out without any other configuration I loved. When I got back into the JVM world, I always wondered if there were such a thing out there. Well I’ve finally found a decent one.

Hello Again and welcome to another blog post in my ongoing series on step-by-step tutorials. This one will actually build atop the last Hello Kotlin one and make a JAX-RS web service. This particular implementation of JAX-RS will be Jersey. Jersey is actually the reference implementation from Oracle, but there are a few out there that I’ve honestly haven’t given enough time. The code repository of everything is located on github for you to follow along.

This is part of a series of blog posts that I’ve always wanted todo. Read about them here. For this step-by-step guide let’s do something basic and get kotlin compiling and running inside a docker container. The companion repository is here. Step 0: Prerequisites I am going to assume you have the following installed and already running. We will be using the local gradle wrapper instance after the initial setup, but you do need it for the initial creation.

Over the course of my development career, I’ve always tend to enjoy tutorials or explanations that guide you through concepts or frameworks step by step. Ones that have a goal and slowly work through things step by step, building upon itself to reach the final destination. All while explaining why this piece fits there or pros and cons of this piece over here. These trainings are usually harder to come by because everyone is looking for a quick fix, or tool that does it for you automagically.

Have you ever tried to talk to a HTTP server via Telnet? As web developers, either front end or backend, we should strive to at least strive to have a understanding of the technologies we build our success on. And I’ve found through out the years that a surprising number of web developers don’t know how it works. So I thought it was fitting to start by looking at the basics of the communication mechanism we build upon and use every day, HTTP.