当前位置:网站首页>The revival of technological minimalism

The revival of technological minimalism

2021-09-15 04:32:40 Jiedao jdon

This is from radicalsimpli.city Manifesto of technological minimalism , Complaints about current complex technologies 、 Criticize .

We seem to enjoy complexity : We use SPA、Vue/React、Transpiling、Typescript、Babel、Webpack、PureCSS、GraphQL、JSON And use on the back end Microservices 、protobuf、Kafka、InfluxDB or NoSQL Database creation complexity .

This complexity is accidental , Not in the business problem domain .

This complexity leads to the need for a solution to manage it —— Usually Kubernetes.

You need to run these things , And there are many micro Services , You need a lot of machines . This led to the AWS.

This brings its own complexity .

Now we need to write React Front end engineer of the application , To write REST and GraphQL The backend engineer of the endpoint , And hold Kubernetes Our operation and Maintenance Engineer . This leads to the use of simulation and local databases 、Docker Image and build pipelines for complex test setup , It takes tens of minutes to run .

It takes a lot of time to do a simple thing , For example, add a field to the form - For example, add a birthday field to your profile . What takes a few minutes now takes a few hours . Then things changed , You'll spend a whole day getting your microservice running again : Skillfully balance each service and each version of each framework and tool over other services .

 

The last thing developers can do is write business logic . If you look at what you're doing and count the lines , Then the least time is to write real business logic , In the code IF.

But this involves having SQL Database to object to JSON Serialization , By routing to React Store in UI.GraphQL、SQL、Javascript Objects and Python Data definition in object . When you need to spend a lot of time around the framework 、 Technology stack and serialization are held during the ceremony , There is not much time left to process business logic .

 

Why should we build complex systems and framework ? Because we want to accept the challenge , But it doesn't go deep into the business field ! So developers themselves invent new frameworks and systems to build their own challenges . They want to try new things .

 

There are many problems . Like Rachel · Kroll ( Rachel Kroll) written : “ The code runs on people . Please keep it simple .”  The same is true of components and systems . Before the code runs on the computer , It needs to run in your mind .

“ If it takes an hour to figure out what happened , that , This hour is not spent doing other more useful and interesting things .”

most important of all , Technology spends a lot of time on itself rather than providing business value . Managing so many systems and components requires knowledge , And because of the edge situation , So there are many mistakes . The combination of these factors can lead to inefficiency 、 Too many developers and high costs .

 

minimalism Radical Simplicity coming

What is extremely simple Radical Simplicity? Minimalism means having as few components and moving parts as possible . Reuse technology for different purposes , Instead of using new moving parts for each purpose . Instead of using Postgres As a database 、Druid As event storage 、Redis As caching 、Rabbit MQ As message queues and Elastic As a full-text search , It's better to use managed Postgres As a database , For full-text search 、html cache 、 Release / Subscription and with TimescaleDB Event storage for .

This enables us to have deeper knowledge 、 Faster action 、 Faster entry of new developers 、 Fewer failures 、 Dozens of framework and component upgrade plans , And more developer happiness . The core of development is to enter the process . Developers are more efficient inside the process than outside the process .

Basecamp yes Rails Creator , What it does is Radical Simplicity.Basecamp Use HTML Wrote their Hey Email application , Not used React.Stack Overflow This is achieved by running their services with a small amount of real hardware . Here's the irony , all AWS Problems are caused by... Running on real hardware Microsoft SQL Server answer . No, GraphQL, No, React, No, Kafka, No, Webpack, either Kubernetes.

You can also use the Radical Simplicity. Radical simplicity is also radical . One is based on HTML The monomer application of : Use... On the browser side Hotwire Turbo With the least Javascript Refresh ; Use managed only Postgres As data storage 、JSON、 Job handling 、 Message queuing database , Column storage is used as data lake and data warehouse . If you can't resist , Please add Redis Cache , because Redis Never interrupt .

 

 

Many startups with only a few customers have multiple microservices 、Redis、Postgres、Elastic、Kubernetes、Webpack、JavaScript SPA、REST API、 with Apollo and Kafka Of GraphQL Or for message queuing or job servers RabbitMQ.

If you compare this with using managed only Postgres( instead of PG、Redis and Elastic)、Unpoly Compare the radical and simple settings , Minimalism is rendering on a monolithic server HTML, And use BigQuery Analyze data warehouse .

The latter is a much smaller architectural setup , Implement the same but need to maintain 、 There are far fewer moving parts to learn and debug . There are far fewer components to monitor .

When some companies own 50 Multiple developers and millions of users , You need complex settings ; Most companies , Especially newly established companies , Do you need that complex setup ? No !

 

版权声明
本文为[Jiedao jdon]所创,转载请带上原文链接,感谢
https://chowdera.com/2021/09/20210909112805262s.html

随机推荐