Taking a page from Maslow's Hierarchy of Needs, this effort examines what microservices need from the org, orchestration, and infrastructure — all with a cloud bent.
These days, many developers work on a project on the same server at the same time — but we still need to be able to schedule app updates the server whenever we want to.
Having functional software architecture can greatly minimize costs, open up possibilities for reuse, and allow you to to translate design endeavors to great heights.
Modern load-intensive apps require a lot of work. You have to be sure that you're using your resources efficiently and getting the highest performance you can.
Moving to a microservices architecture is not just a matter of replacing method calls with HTTP requests. Welcome to the world of containers, reactive stacks, and more.
When moving from a monolith to a distributed system, tracing and debugging can get really hard. Luckily, there are some things you can do to make it easier.
Hexagonal Architecture divides work inside and outside of an app instead of into layers. This overview covers the benefits and uses of the Hexagonal style in your work.
Configuring Java security policies is an important but extremely time-consuming task. See, how much work it takes for a small project like Spring Pet Clinic.
If compliance and security are a concern, you can set up Cassandra clusters with encryption in mind using SSL while ensuring nodes can still communicate with each other.
Creating an Octopus step template to create and push a Docker image to DockerHub is a good way to move from a VM to Containers while keeping the current infrastructure.
This in-depth look at how to Spring Boot Docker images to the Amazon EC2 Container Registry provides a good example of Spring, Java, the cloud, and container usage.
It's tempting to provision more memory to your VM than you need, but that can cause headaches—and containers might make it worse. The answer lies in auto-scaling.
CORE
