Miguel García López

As par of my eventual collaborations as a trainer, which I enjoy a lot, I implemented a two-week-long course introducing back-end systems programming to students taking a broader course on modern development technologies.

I started by introducing concepts on (SQL and noSQL) databases, dissecting the HTTP protocol, and presenting the REST paradigm for building APIs, auth* and security issues, etc.

A practical section was comprised of modeling and developing a simple secured HTTP REST API talking to a database, using the Java EE stack.

I have occasionally done trainings on several technologies and frameworks.

This repository holds the code samples I have used for a two-day training course on JPA and Hibernate, and working with databases from Java in general.

It features:
- Maven based projects handling dependencies, specific-purpose plugins, and profiles.
- Many JPA mapping samples.
- Generation of DB schema from JPA annotated entities.
- Lombok-powered.
- Liquibase build and runtime integration to handle DB schema migrations.
- Generation of metamodels as part of the build phase.
- Usage of QueryDSL as a friendlier alternative to JPA Criteria for typesafe queries.
- jOOQ code generation from DB as an complimentary means to access the DB from Java.

This is a sample project I wrote as the source companion for a presentation I issued during a local talk introducing Angular 2.

Hazelcast is an awesome middleware providing distributed data structures, caching, pub/sub mechanisms, and much more.

It is perfectly possible to just download its distribution and start a node via java -jar, pointing it to your configuration, etc.

This (maven) project takes an alternative approach and builds a ZIP file bundling Hazelcast (and other) dependencies, a directory structure for libraries, configurations, etc., and SLF4J-based logging using logback as the underlying implementation.

A sample project I wrote over the idea of a microservice that consumes a third-party API and then processes and aggregates the data in a custom form.

This idea is implemented in two rather different ways for illustration and practicing purposes. One is a pure Java EE approach using the great latest features from its v.7 specification. The second is a solution on top of Vert.x, a Java-based purely event-driven framework.

Their two programming models are rather different. Implementing the same features on top of each is great for comparing.

I wrote this post about the Lombok tool for a well-known editing site on Spring and misc. Java development articles.