This blog describes a basic Microservice architecture design using Play 2.4.X and Scala. The big idea behind microservices is to architect large, complex and long-lived applications as a set of cohesive services that evolve over time. The term microservices strongly suggests that the services should be small.
In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API.
Single node microservice architecture
Multiple node microservice architecture with load balancer
Dive into code level activities
Scalastyle : Check the code quality
To check code quality of all the modules
$ ./activator clean compile scalastyle
Scoverage : Check code coverage of test cases
To check code coverage of test cases for all modules
$ ./activator clean coverage test
By default, scoverage will generate reports for each project seperately. You can merge them into an aggregated report by invoking
$ ./activator coverageAggregate
Deployment : microservices
$ ./activator "project <service-name>" "run <PORT>"
6 thoughts on “Play 2.4.X : Microservice Architecture using Play and Scala1 min read”
Reblogged this on Play!ng with Scala.
Reblogged this on himanshu2014.
Reblogged this on knoldernarayan.
Reblogged this on Rishi Khandelwal.
Wouldn’t it be better if each microservice had its own database, so each service owns its data.
Microservices split one large application into small independent parts, this should also apply to the database.
Comments are closed.