Preference to Bottle Over Jar! Why?
- I have heard Bottleneck often and consistently; but, not Jar Neck . Why?
- Be it in Software Engineering or day-to-day life problem solving description,
- The Bottleneck is referenced and not a Jar Neck.
Looks like people want Bottle but not the Bottleneck speed and benefits. Bottle without its neck is a jar?!
Bottleneck exist for better controllability.
- In a bottle, the bottleneck is a solution! It is not a problem!
- It is to mitigate any risk and problem that arises from the flow of content in the bottle.
Yet we describe, learn and communicate the neck of a bottle as a relativity and analogy to a problem.
- The Gateway can be seen as a neck of a bottle which controls the incoming requests and outgoing response.
- Gateway is a necessity.
- We need Gateway to be adaptable in size of its neck based on traffic volume it is handling. Here, the gateway's neck size should adapt and scale contextually.
- When describing a problem, we are talking about how this bottleneck size which is not adaptable for the context.
- That adaptability has to be built in engineering to scale in any dimensions and magnitude.
- When this is not done, we equate the software system's problem to a bottleneck as a analogy, which is incorrect! The bottle has got its size and its neck size fixed for a purpose and as a solution.
- The context of a bottle and today's any systems are different.
- It is good to draw similarities from General Systems Thinking and observations.
- But the solution cannot be generic to all systems; it has to be contextual. The software system has to have its contextual solution.
So, next time when someone in your team or network talk about bottleneck, do share them bottleneck is for better controllability. Having a contextually resizable and adaptable bottleneck is the need for Software Engineering; not the elimination of bottleneck.
In fact, a software system should have and will have a bottleneck in a point. And, this bottleneck will be adaptable to the context for having what it should let through and process.
Is the runway of an airport a bottleneck when it is compared to a sky? Is that a solution or a problem? Likewise, the ship will have a defined route path and it does not sail without a route path. Is this a bottleneck to ship and its business? A elevator can accommodate the defined number of people or kilograms allowed, and not beyond that to move. Is that a bottleneck? The esophagus in human body has a size which medical science observes as normal and acceptable; any deviation from that size measurement, the medical science test investigates it as a risk and problem. Why? Is the circumference size and length of esophagus a bottleneck to human anatomy and physiology system?
The engineering solution will and should have a bottleneck at a point. Having a adaptable bottleneck to the context is one what tries to accomplish in a software system's scalability and operability.
Please, do not equate solving a "bottleneck" situation with Agile practice. Does it look like a joke? I will not be surprised if someone says bottleneck problem is solved if practiced Agile.
