HNHacker News
TopNewBestAskShowJobs

ashish5887

72 karma · joined December 4, 2015

submissionscomments
ashish5887··on [dead]
what kind of interesting failures have you seen because of caching
ashish5887··on Rip Creator of Cut/Copy/Paste
Ty!
ashish5887··on Ask HN: Ever worked with a service that can never be restarted?
What good is a memory dump if you don't have the codebase to navigate? without the code and structure of how its managed a memory dump would just look like an alien language.
ashish5887··on Microservices and Testing – Lessons Learned
Also the process of updating the snapshot should be dead simple!
ashish5887··on Microservices and Testing – Lessons Learned
Good question - In theory the frequency depends on the factor of how frequently other teams are introducing breaking changes in terms of API. If the dependency is too early in development phase and API is changing a lot, then probably that api should not be consumed (internally we don't allow such api to hit prod). But still its a good practice to update snapshots (like you said for stale/seed data) and I have been part of teams that have daily or weekly schedule jobs to run these updates (Both approaches work fine).