{"id":778,"date":"2018-11-01T14:46:00","date_gmt":"2018-11-01T06:46:00","guid":{"rendered":"https:\/\/opentrons.com.cn\/?p=778"},"modified":"2024-04-19T15:21:36","modified_gmt":"2024-04-19T07:21:36","slug":"the-synbio-stack-part-1","status":"publish","type":"post","link":"https:\/\/opentrons.com.cn\/en\/news\/the-synbio-stack-part-1\/","title":{"rendered":"Synbio stack, part 1"},"content":{"rendered":"\n
I ask myself a few questions every day: How do we feed 10 billion people without creating deserts where we once had farms? How can we ensure that we don\u2019t all die from disease without limiting health to those who can afford luxuries? How can we expand manufacturing output to enable higher living standards for more people around the world, while reducing ecological impact and halting climate change? To me, these are the big questions of the 21st century. They all have biotech answers. The only problem is that today we are not creating biotech answers fast enough to meet our overwhelming demand for solutions. That\u2019s why we need the Synbio Stack. We need a technology ecosystem that increases humanity\u2019s ability to build biotech solutions a hundred or even a thousand times. This article is about that ecosystem\u2014the \u201ctechnology stack\u201d being created that will help us create the world-saving biological solutions we need.<\/p>\n\n\n\n
A \"stack\" is a combination of technologies that can make enormous complexity manageable. They mask some of the complexity by dividing parts of large systems into \"layers of abstraction,\" so designers can focus on the parts that need to be designed at the moment without having to think about all the other complex parts. Stephen Wolfram elaborated on this idea in 1986:<\/p>\n\n\n\n
\"The components of a system should be arranged in some form of hierarchy. Components higher in the hierarchy should provide overall control to the set of components lower in the hierarchy, which can be viewed as individual units or modules. This principle Crucial for software engineering, where modules are often subroutines, this is also reflected in the existence of organs and specific body parts, apparently reflected by subroutine-like structures in the genetic code.\" \u2014 \u2014Complexity Engineering Methods (Stephen Wolfram, 1986)<\/p>\n\n\n\n
For something as complex as a CPU with billions of transistors or a cell with trillions of molecules, organizing things in this hierarchical way is crucial to any kind of engineering work. Wolfram continued:<\/p>\n\n\n\n
\"An important aspect of modularity is that it enables abstraction. Once the construction of a particular module is complete, that module can be treated as a single object, and no matter where the module appears, only its overall behavior needs to be considered. Therefore, modules ization divides the problem of building or analyzing a system into multiple levels, making it possible to make each level manageable\u201d - Complexity Engineering Methods (Stephen Wolfram, 1986).<\/p>\n\n\n\n
By breaking a large complex problem into smaller, simpler parts and stacking them on top of each other, complex problems become easier to solve. A famous example of web development is the LAMP stack (Linux, Apache, MySQL, PHP). If you do a Google search, you'll find many tutorials on how to create web applications using the LAMP Stack, along with diagrams explaining it like this:<\/p>\n\n\n\n