Microservices: don’t use them yet!

Jack Yeh
TeamZeroLabs
Published in
5 min readDec 26, 2019

--

Here is my story:

  • Worked at a startup. One technical founder there.
  • They had a Rails Monolith working and running.
  • Took me on to implement a 3rd party integration that takes remote feeds and ETL record into database. (Pilot requirement)
  • Pilot is a success! More funding unlocked! Technical founder starts to read up on the latest tech buzz words.

AWS/Docker/Microservices

Oh no. They are here.

“The pilot was a success. We need to hire fast and 10x our deployments this year!”

“I will be able to get a remote team up and running.” (To his credit, he did pull this off)

“We should change the following to meet the demand”

  • Change from Rackspace to AWS.
  • Change from Rails to Express.
  • Change from MongoDb to Mysql.
  • Split backend into microservices.
  • Rewrite frontend from Rails to React.
  • Rewrite deployment from Nginx+Passenger to Docker.
  • Not just Node.JS, use es6 with babel.

You and what army?

At that point, we have 3 engineers (counting yours truly) in the bay area. And, a team of 5 remote:

--

--

Jack Yeh
TeamZeroLabs

I monitor your full stack deployment in production, so you can sleep at night. Docker | Kubernetes | AWS | Prometheus | Grafana