Building Microservices with Netflix OSS, Apache Kafka and Spring Boot – Part 3: Email Service

ICYMI: The next step of building our system is the email service. It will be a microservice configured to listen for the USER_CREATED_TOPIC that comes from the user service. Here we will build a UserDto and configure the Kafka consumer to transform the incoming payload to it. Similarly to the user microservice, here we will have an EmailService where the business logic will be executed. This EmailService will be using the UserDto from the payload, transform it to a Mail entity, save it in the database, and send the mail.

In addition to Eureka Discovery; JPA; H2; Kafka; Config Client; to the new Spring Boot project(ms-mail) in SPRING INITIALIZR, it is necessary to add aMail dependency as well. So the pom.xml looks like: https://goo.gl/8ZD9MF #DataIntegration #ML

Intro to API Caching With Zato 3.0

One of many features that the upcoming Zato 3.0 release will bring is API caching – this post provides an overview of the functionality that is already available if one installs Zato directly from the source code.

What’s New

* In-RAM caches accessible to Python-based services and external clients (including REST and other format or protocols)
* A convenient set of practical cache commands based on real-world needs
* GUI and cache contents search
* HTTP channel caching
* Integration with Memcached

Built-in Caches

In-RAM caches are perfect for rarely changing yet frequently read business data. For instance: https://goo.gl/avvzkC #DataIntegration #ML