Overview

This article completes the topic of defining a Java Spring Boot microservice using a Note Web PaaS DSL service blueprint. Previous article of the series has walked you through defining such a microservice with an embedded database. This time we'll define an RDS MySQL backend in the same AWS account, with the ECS cluster running the Java Spring Boot microservice called NoteWebPaaSDSLDemoSpring. 

Solution Walkthrough

Please watch the video below for instructions how to turn your Java Spring Boot microservice backed by an embedded database to use AWS RDS MySQL data container:

• define "database instance" statement nested in the "cloud" Note Web PaaS DSL statement
• define tables using "entity" and "field" statements
• add following attributes to the "container service" Note Web PaaS DSL statement
  • "database type" - to specify type of database to connect to
  • "database url" - to reference name of the database instance, cluster deployed in the same blueprint OR referenced through "resource" statement

Publishing a microservice under subdomain in a hosted zone of your AWS account is easy:

• add "registerdns" attribute to "container service" Note Web PaaS DSL statement

Conclusion

This article continues the topic of using Note Web PaaS DSL blueprints to define AWS microservice landscapes, adorning an AWS ECS service with RDS MySQL connection and a user-friendly Route53 DNS name. This approach emphasizes core architectural elements and most relevant details in the blueprint code, leaving secondary and repeated details in the generated Ansible, Terraform code, still at your full control.