ashish5887

9 ms·

31.
Microservices Q&A(microservices-on-my-mind.blogspot.com)
2 points by ashish5887 8y ago|0 comments
32.
Microservices – Q and A(microservices-on-my-mind.blogspot.com)
3 points by ashish5887 8y ago|0 comments
33.
Ship Code Faster – Lessons Learned in Evolving Delivery Pipeline(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
34.
Microservices and Delivery – Lessons Learned(microservices-on-my-mind.blogspot.com)
2 points by ashish5887 8y ago|0 comments
35.
Brain dump of microservices in series of blog-posts(microservices-on-my-mind.blogspot.com)
2 points by ashish5887 8y ago|0 comments
36.
The What and the How of Building Software(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
37.
The What and the How of Building Software(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
38.
Why microservices fail?(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
39.
Why microservices fail?(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
40.
Adoption of Microservices and Lessons Learned – In series of blog posts(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
41.
Dark Launch and Feature Toggles(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
42.
Dark Launch and Feature Toggles(microservices-on-my-mind.blogspot.com)
2 points by ashish5887 8y ago|0 comments
43.
Microservices and Local Chaos-scenario tests(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
44.
Test local Chaos-scenarios in a Microservice stack(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
45.
Lessons learned in evolving Developer Experience(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
46.
Microservice Adoption – Evolution of Tech Stack(microservices-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
47.
by ashish5887 8y ago
Also the process of updating the snapshot should be dead simple!
48.
by ashish5887 8y ago
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
49.
Microservices and Testing – Lessons Learned(microservice-on-my-mind.blogspot.com)
2 points by ashish5887 8y ago|3 comments
50.
Microservices and Testing – Lessons Learned(microservice-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
51.
Microservices and Developer Experience(microservice-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
52.
Microservices and Tech Stack – Lessons Learned(microservice-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
53.
Microservices and Testing Pyramid(microservice-on-my-mind.blogspot.com)
1 points by ashish5887 8y ago|0 comments
54.
Ask HN: How to attract best talent
2 points by ashish5887 10y ago|1 comments