Published in


Microservice or Monolith?

Why not both?

Colored Rocks
Image by sarajuggernaut from Pixabay

There are lots of reasons that people argue for microservices. But the monolith has one big reason…simplicity. One service that does it all, only one set of source code. The boilerplate associated with a service doesn’t have to be duplicated. And sharing code isn’t a problem.

My previous article on contextual logging required a couple of services, but I didn’t want to…




A humble place to learn Java and Programming better.

Recommended from Medium


A brief info on Linker, Loader, Symbol & Symbol Tables

An Intro to TDD using RSpec in Ruby

Difference Between Keywords and Identifiers

FastAPI, Deta, and YCombinator

Code Smell 47 — Diagrams

Creating AR Multiplayer App in Unity

Creating AR Multiplayer App in Unity

Stop Calling them ‘Bugs’

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Randal Kamradt Sr

Randal Kamradt Sr

Java software engineer for Coinme Inc. Artist and musician.

More from Medium

Spring Boot Tests with Kotlin and Embedded Kafka

Unit Testing Apache Camel

Multiple Level Inheritance for Builder Pattern in Java

JUnit5: Parallelization of Parameterized Tests (Only)

JUnit5 Parallelization Configurations