What will you accomplish by end of April?
- Move microservice architecture to a monolith
- Make reporting features as robust as possible for employee use, with their continued feedback
What did you do yesterday to work towards your goal?
- Really grokk'd the MongoDB Aggegation Pipeline and refactored old code to make it more maintainable
What will you do today?
- Release a small feature exposing more search params on the pipeline endpoint to let users query more openly on their datasets
Happy hacking, everyone!
Hi Jaikamat,
Just reading your post made me curious about:
"Moving microservice architecture to monolith".
If you don't mind sharing, why did you decide to do so?
I’ve found the constant deployment and upkeep of both test and production lambda functions to be quite cumbersome, and since the app is used by only 5 or so users (and scalability isn’t a concern), consolidating my endpoints for easier maintenance makes more sense for my use case
Thanks for your reply and it's soo true! A simple monolith speeds up everything especially during prototyping. Being a developer myself as well and after years of microservices indoctrination I only start with a monolith. You can always easily take the less performing components out if you have to.
If you end up having a scaling problem, you're in a luxury position as most often it's synonymous for many users.
Glad to hear that you too have a similar outlook! As a solo contributor it’s sometimes difficult for me to clearly discern best practices. In this case the “gut feeling” did the trick.
Going forward, will definitely take your advice to start with a monolith - can always break out from there :)