prabhatjha

8 ms·

61.
Wootric: Analyzing customer feedback using machine learning(cloud.google.com)
8 points by prabhatjha 9y ago|0 comments
62.
Engineering war stories and lessons learned in 2016(wootric.com)
43 points by prabhatjha 10y ago|4 comments
63.
by prabhatjha 10y ago
ACID was just an example. Thanks for clarifying it though.
64.
by prabhatjha 10y ago
Multi-tenancy at scale with RDBMS is just hard to do. Once you get to certain volume, you just have to have different data stores for different needs. Only a subset of business require ACID properties so you would use RDBMS for those and fo
65.
Optimizing the Performance of an Analytics Dashboard(wootric.com)
20 points by prabhatjha 10y ago|3 comments
66.
by prabhatjha 11y ago
What do you mean that your code to ApiEditor was shared privately? Everything about Swagger-UI, Swagger-Editor is open source so I don't understand why you need to share privately.
67.
by prabhatjha 11y ago
You are correct that it needs more documentation and will have it asap. Two things you can do right now: 1. Using "Try this operation", you can hit your API and you will get a mock response. 2. Project-> Download Node.js Projec
68.
API Studio – build, test and share APIs in Swagger(apistudio.io)
27 points by prabhatjha 11y ago|8 comments
69.
by prabhatjha 12y ago
My vote is definitely for swagger. Besides being a great way to write API spec, it has tons of tooling to take a given spec to the next level. See the list at https://github.com/swagger-api/swagger-spec . My favorite is
70.
by prabhatjha 13y ago
It just made my day.