Search results
Results From The WOW.Com Content Network
In this post, we'll describe the differences between push and pull systems and provide some examples to help illustrate why pull system is often preferred when it comes to following lean principles. Download our Ultimate Guide to Lean Manufacturing →
A pull system initiates production as a reaction to present demand, while a push system initiates production in anticipation of future demand. In a pull system, production is triggered by actual demands for finished products, while in a push system, production is initiated independently of demands.
When creating a distributed system, there are two basic architecture patterns you can follow (and they can be mixed in the same system, if you choose). First, what I call “push” architectures ...
"Push type" means "make-to-stock," in which the production is not based on actual demand. "Pull type" means "make-to-order," in which the production is based on actual demand. (Lean Manufacturing Japan) Is it really? Often, push and pull are (incorrectly) explained through “make-to-stock” and “make-to order.”
This API arrangement is characterized by a client who actively pulls requests from a server to get the required data. This is similar to the ‘pull’ model where the client gets information from the server at will when it requires it.
The main difference between push and pull manufacturing is that in a push system, production dictates how much of the product will be “pushed” to the market while in a pull system, current demand “pulls” the goods, i.e. it dictates when and how much to produce.
A team using iterative/incremental/agile techniques could use a push system, while a team using sequential development could use a pull system. However, typically, the agile methods (XP, Scrum) favor self-organizing teams and therefore pull systems.