1. When you consider microservices to be THE solution regardless of the problem.
2. When you think a microservice architecture is just what you need for your indie hacker side project currently with no users, pre-revenue and seeking product market fit.
3. You think microservices will ‘make things faster’.
4. If you think a mircoservice architecture is ‘simpler’.
5. When you have an IT operations team focused on preventing change from upsetting the smooth running of the system and a development team whose sole purpose is changing the system. HINT: combine them via devops
6. When the deployment of a new server into production is a painstaking and manual task of provisioning, updating and patching.
7. When you don’t consider how team topologies affects the architecture and architecture affects the team topology.
8. When you think a ‘monolith’ architecture is a ‘bad thing’. Why? Just because…
9. When your deployment process is painful involving multiple handoffs, approvals, signoffs and you don’t have a simple repeatable auditable deployment process. Microservices mean more deployments compounding the problem.
10. When you are manually handling server configuration, software deployment, scaling, and incident and log management.
And this is coming from a fan of microservices architecture.
Hope you enjoyed the post. Interested to hear your thoughts on microservice architecture.
Happy to announce we at terrabyte are joining the NDRC national startup accelerator, Ireland’s national startup accelerator programme for globally ambitious tech entrepreneurs in Ireland.
Our developer showcasing platform thefullstack.network was chosen along with 6 other companies out of a total of 300 applicants.
The accelerator is run by Dogpatch Labs Startup Hub and comprises of investment plus mentoring and support. I’m particularly impressed to date by the focus on mentoring and am excited to see how we will evolve over the next few months.
The Full Stack is a platform designed for software engineering that I wished had existed throughout my career and to this very day. We’re hoping this platform helps engineers, managers and teams on their journey:
Showcase you and your projects on a professional network specifically for Software Engineering.
Connect with like minded engineers and build a more meaningful network (no spam!).
Don’t let your work get overlooked, instead let it connect you to opportunities from Teams and Engineering Managers looking for engineers just like you.
Unlike other networks liked LinkedIn, when “real” engineering hiring managers reach out to you on The Full Stack, you get paid into your wallet for reading and responding to opportunities, putting you in control.
The platform is built in Next.js, Tailwind, Spring, NodeJS, MongoDB running on Google Cloud Platform.
I’d really appreciate your feedback and thoughts. Reach out!
Last year I completed the AWS Cloud Practitioner certificate exam. There are similarities but I did find the GCE exam tricker. Both consist of 40 or 50 multiple choice questions with 4 possible options. The AWS exam focused on more high level knowledge of the AWS services and selecting the best AWS option to suit a generic use case. The GCE exam however digs deeper into more practical day to day cloud engineering working knowledge. In particular you’ll need to know the essential gcloud, gsutil commands and IAM.