Posts Tagged: cons

Should You Start With A Monolith or Microservices?

Challenging Conventional Wisdom

Conventional wisdom suggests that a new project should start with a monolithic server because a unified application can make the workflow easier for a small start-up team. But microservices can be a valuable alternative in the right circumstances. Read more

Writing Microservices in Go Part II – When Not to Use Go

In Writing Microservices in Go pt. 1, we highlighted a whole bevy of reasons for coding in Go, the novel, forward-thinking language developed at Google. However, there are two sides to every coin; the benefit of a language or system can often be a drawback in other use cases, and a host of hidden faults can make what was once an awesome idea significantly less awesome. Read more