In the last few posts of our microservice journey we created a compartment, launched a Kubernetes cluster and set our tenancy up for a Docker user and registry and created an Autonomous DB instance that we can use for data persistence. In this post we will start to take a look at writing some actual microservice code. I want to reiterate that each application has unique requirements that should be evaluated before you choose to implement any solution and so the choices that I make in this blog series might be different than the choices your organization will make. The important questions to ask yourself are:

· Are microservices the right tool for the job?

· Will this solve my problems in a maintainable way?

· Can our budget afford the cost of implementing this solution?

These are important questions to ask yourself, because introducing a new way of thinking can bring up issues that are difficult to resolve later on.

Microservice Patterns

Before we dive into the code, let’s start by defining a few patterns for microservice data management. The easiest patterns to digest when it comes to microservices are the shared database and database (or schema) per service patterns so let’s start with those patterns. Read the complete series: Part 1, part 2 and part 3

Developer Partner Community

For regular information become a member in the Developer Partner Community please register here.

Blog Twitter LinkedIn Facebook Meetups

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic