Something I’ve recently wrapped my head around is the difference between development errors versus runtime errors. For much of my career I’ve approached all errors as runtime because then you can fail gracefully. But, that’s a mistaken approach and it adds unnecessary complexity. Let’s say, for example, your web app fails to instantiate a required …
The documentation I wrote for the Git Pull requests: Alrighty! There’s a script/cron running on 172.18.18.107. It runs every 60 mins. To make a staging release: Go to DevOps or setup a pull request in CLI: Create a new pull request. Make sure You are in either od-dashboard-dev or ui_development depending on what you want …
I’m taking a Node.js microservices course to stay up-to-date. This course is going through the process of building a service registry before going into microservices. It occurs to me, why are we re-building a service registry for every app? Why is there not a Server Registry as a Service? I.E. Why not a “domain name …
https://auth0.com/blog/node-js-and-typescript-tutorial-build-a-crud-api/
I started writing a scheduled jobs management tool and now realize it was a mistake. The original problem I was trying to solve was “how to you setup scheduled jobs on multiple servers (dev, staging, QA/UAT, production) while also saving the run schedule to version control”. I was over-complicating this in my head and thinking …
https://blog.logrocket.com/building-microservices-node-js/
No criteria is perfect and they inevitably take some time to refine and perfect. But! I think this is a good representation of my understanding of SDLC, my communication, and my management style.
I wrote about microservices and micro-UIs the other day and that got me thinking about another value in microservices; as a single source of truth. In this case the same can be said of shared classes & functions. This is an argument against code duplication. Let’s say for example, and I’m currently seeing this in …
Functions & Microservices As A Single Source of Truth Read More »
I think we’re all sold on the idea of microservices; they reduce risk, improve maintainability, and reduce fragility. When you think about it, everything in the Software Development Life Cycle (SDLC) is all about reducing down to the small possible increment. With user stories & requirements we want to boil down to a very small, …
Massive credit and thank you to Log Rocket for generating so much valuable, fee content.
