In this post I’d like to make a little journey through the Pivotal Cloud platform known as “Cloud Foundry”. I did it by deploying two microservices and consuming internal service like Config Server, Circuit Breaker and, obviously, Service Registry.
Are you looking for a database that works as key/value pairs? High performance, obviously nosql and with disk persistence?
If the answer is “yes” but even if you’re not sure of what could be the solution, I’d really suggest to have a look at RedisDb, a good solution adopted for big performance challenges such log collections or page view ranking.
Spring Cloud Stream improves the opportunities to distribute the task computation into different micro services using a message driven methodology.
Using a pattern based on source, process and sink, we’re able to build pipeline for resolving common issue as log processor. This is what I’m going to do in this article.
I’ve learnt that modeling a schema for a NoSQL database (Mongo, Cassandra, …) is not the same thing of drawing a schema for SQL one (Oracle, MySql, …).
In this article, I’m going to illustrate what I’ve learnt reading by who knows more than me!
Sometimes an object instance is not enough; specially, when you use a stateful classes on concurrency environment runtime, a pool of object is a good solution to achieve a multithreaded executions.
In this article, I’ll show you how to set up this configuration with Spring.
Distributed applications is always a current topic in the articles and forum discussions; Microservices answers the need for application scalability and makes a good marriage with Cloud solution (AWS) or Virtual container (Docker).
In this post I’d like to do a little introduction of the concept behind these solution type.
In my previous post on the argument (Junit testing with Spring), I skipped a very interesting part of testing attributes in the code which are inside methods.
In these cases, Mockito it’s very helpful to solve the problem.