Since the last blog post, we have implemented:
- an improved design for the search criteria drop box
- proper icons for badges as opposed to a placeholder img tags
- mapping in badges dynamically from preset list as opposed to a predetermined amount of objects hardcoded
Next up to work on/finish are:
- having icons work properly (likely just an issue with my updates not pushing to github properly)
- implementing primary and accent colors that work dynamically for each badge (likely through a reflexive attribute of some sort on the badge tag)
- having the author text field loading properly with the rest of the fields (not sure why but its staying to its default value from the constructor
- implement the "searching" or rather filtering of badges instead of mapping the entire list of badges in
User interaction pattern diagram:
Real world micro-service use case(s):
- Microservices are typically preferable in cases where you want to aim for speed and scalability
- One example in which this helped was in Walmart in 2012 when high load caused a string of system issues during seasonal peaks of activity
- Walmart re-platformed core businesses tasks to microservices to help address this, their change resulted in: hardware costs dropping between 25-50%, 40% less power usage, prevented downtime during the aforementioned seasonal peaks, and improved integration with their mobile app resulting in more sales, and in turn, revenue.
Current preview:
The current Vercel deployment and code are viewable here:
Top comments (0)