Can i send a scheduled order in zerodha pi
- #Can i send a scheduled order in zerodha pi full#
- #Can i send a scheduled order in zerodha pi software#
- #Can i send a scheduled order in zerodha pi code#
KISS, don’t be afraid, and boring > cool. On the other end of the spectrum is being lazy ignoring common sense principles leaving them for later.
#Can i send a scheduled order in zerodha pi software#
Also, not every piece of all software has to be low latency and high throughput to begin with. Trying to build for “web scale” on day one can turn out to be painful as the careful premature optimisations get thrown out of the window as the business and user requirements change unpredictably. Then refactor and improve as time progresses. In the beginning, focus on writing good-enough software. Everyone has heard it, appreciates it, but finds it difficult to practise. … is the non-tech equivalent of “premature optimisation is bad”. One moves on to scaling resources horizontally or vertically after exhausting all easy optimisations in application code.
![can i send a scheduled order in zerodha pi can i send a scheduled order in zerodha pi](https://zerodha.com/z-connect/wp-content/uploads/2015/01/9-1.jpg)
![can i send a scheduled order in zerodha pi can i send a scheduled order in zerodha pi](https://tradingqna.com/uploads/default/original/3X/5/d/5d40a0056a923dc2db55ef5d8fa84a40bd93312f.png)
#Can i send a scheduled order in zerodha pi code#
Scaling starts bottom-up with good code and good software. Although the outcomes quantified strictly by numbers seem equal, they are not. Scaling starts with well built software.Ī poorly written Python web service may be able to handle 1000 requests / second using $100 worth of resources, while a well written one may be able to handle the same rate with $25 worth of resources. Internal context and awareness is more useful to scaling than external validation. They only make sense within their specific environments.įor that reason, tutorials and articles that demonstrate great scale under narrow constraints ( “How we opened 10 million concurrent WebSocket connections with a potato battery” … while transmitting zero data), while are good to satisfy academic curiosity, should not be treated as general purpose user manuals. So, request rates or database sizes, or any such 1:1 comparisons across organisations are pretty meaningless.
#Can i send a scheduled order in zerodha pi full#
Querying a database with a billion time series data points is not equal to doing a full text search on a billion rows, or even a fraction of that. Comparisons are almost always meaningless.Īn application that serves 1000 requests per second of static data is not the same as one that serves data from a database.
![can i send a scheduled order in zerodha pi can i send a scheduled order in zerodha pi](https://www.adigitalblogger.com/wp-content/uploads/zerodha-pi-compressed.jpg)
These should be consumed with a healthy and rational awareness of context and trade-offs. I have been getting a number of “how do I scale my service?" queries lately, and hence, this assortment of conceptual and technical notes from practice and production at Zerodha, in no particular order.
![can i send a scheduled order in zerodha pi can i send a scheduled order in zerodha pi](https://zerodha.com/z-connect/wp-content/uploads/2019/07/GTT-1-1.png)
This is specifically in the context of running software systems that serve concurrent user traffic and demand. That said, there are several, mostly trivial, common sense techniques and rules of thumb that help pluck the low-hanging fruits of typical scaling problems. It is a collection of practices unique and intimate to every organisation, and is the product of an infinite number of variables the numerous domain-specific problems, the structure of the organisation, the nature of the people involved and their biases, countless engineering decisions and trade-offs, technical debt and history, ad infinitum. “Scaling” is not a specific technique but an entire spectrum that stretches all the way from “Google scale” to the K8s cluster Karan runs on a Raspberry Pi plugged into a 12V shaver outlet in his bathroom to encrypt his DNS queries for peak privacy, while he asks Alexa to dim the lights and play his favorite non-mainstream indie music.