blocks|key|5409873|text|我完全同意，只要有可能，加密应该只由专家完成。它也应该是开源的，并经过了大量的同行评审。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5409874|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I fully agree that encryption should only be done by experts whenever possible. It should also be open source and have undergone a good deal of peer review.

blocks|key|5409911|text|我一直使用第三方控件的领域是图表。这是一个相当常见的问题，必须为一些批次的数据绘制图表，并且第三方控件是成熟和值得信任的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5409912|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The area where I have consistently used third party controls was charting. It is a fairly common problem to have to chart some batch of data and the third party controls are mature and trustworthy.

blocks|key|5410119|text|我的经验法则是使用(或至少考虑)第三方来处理任何超出业务核心目的的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5410120|加密一直是这方面的典型例子。但它也延伸到了其他领域。|5410121|在开发期间编写用于故障排除的日志记录代码与编写用于监视生产系统的日志记录代码完全不同。|5410122|这一切都是关于选择哪些开发领域真正为您的项目增加了价值。使用第三方工具可以消除该组件不完整/有but等风险，但同时也会带来风险，即它可能不像您需要的那样灵活。|5410123|另一个例子是为一个网站开发一个完整的网络论坛，当你可以用更便宜的价格购买一个解决方案时。|5410124|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

My rule of thumb is to use (or at least consider) third-party for anything that's outside the core purpose of your business.

Encryption's always been the prototypical example of this. But it extends to other areas as well. 

Writing logging code for troubleshooting during development is entirely different than writing logging code used for monitoring production systems.

It's all about choosing which areas of development actually add value to your project. Using third-party stuff removes the risk that that component is incomplete/buggy/etc. but comes with the risk that it may not be as flexible as what you need.

Another example would be developing an entire web forum for a website, when you can buy a solution for much cheaper.

blocks|key|5410179|text|大多数情况下，加密应该是第三方的，...unless你是在销售加密系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5410180|这就是我所理解的Atwood先生的观点，你的核心业务不应该是第三方的，所以可能没有什么应该总是第三方的……|5410181|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Encryption should be third party most of the times, ...unless you're in the business of selling encryption systems.

Which is pretty much Mr. Atwood his point as I understood it, your core busines shouldn't be third party, so there's probably nothing that should always be third party...

blocks|key|834177|text|我想答案取决于用法。如果你的开发是为了盈利，如果使用组件的成本与开发组件的成本相比产生了更多的利润，那么你可能会购买组件。当您没有生产大型组件的内部专业知识时，情况尤其如此。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834178|我用过的几个很好的例子是Infragistics控件和Dundas图表。虽然我们可以在内部创建这些，但与购买几个许可证相比，在时间和机会方面的成本将是巨大的。|834179|当然，有时我们做这类事情时甚至不考虑它是一个组件购买。稍微想象一下，您可以包括.NET框架、SQL+Server、Windows+API等。|834180|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I guess the answer depends upon the usage. If you are developing for profit, you would be likely to buy in components if the cost of using the component vs the cost of developing it results in more profit. This is particularly the case with large components when you do not have the in-house expertise to produce them.

A couple of good examples that I have used are the Infragistics controls and Dundas charts. Although we could have created these in-house, the costs in terms of time and lost opportunity would be huge compared to buying a couple of licenses.

Of course, sometimes we do this type of thing without even considering it as a component purchase. Streching the imagination a little, you could include the .NET framework, SQL Server, the Windows API, etc.

blocks|key|3999382|text|那得看情况。是否有第三方库可以满足您的需求，最重要的是，您使用的语言和/或API。那就去做吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3999383|如果你有理由做你自己的版本，确保它不只是“不是在这里发明的”。此外，如果你还没有深入了解市场上排名前五的领先产品，无论你需要什么，你的工作都做得不够彻底。你很有可能找到你正在寻找的东西，即使你不能使用它，你仍然可以从库的描述中学到一些东西。至少你会知道你需要哪些功能，哪些不需要，如果你还把源代码放到了其中一个库中，这应该是你的首选，而不是没有源代码但可能有更多功能的竞争对手的库。|3999384|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It depends. Is there a 3rd party library available that suits your needs and most importantly, the language and/or API you work with. Then go for it.

If you have reasons to do your own version, make sure it's not just "not invented here". Also, if you haven't had an in depth look at the market's top five leading products for whatever you need, you haven't done your job thoroughly enough. There are good chances you will find what you are looking for, and even if you can't use it, you still learn something even from the library descriptions. At the minimum you will learn which features you would need and which you don't. If you also get the source code to one of the libraries, this should be your preferred choice over a competing library with no source code but possibly more features.

blocks|key|5410429|text|不要忘记，时间对于手写所有的东西来说是一个大问题，这并不是说你不能这样做，而是问题来自于你的客户或公司，他们总是想要找到最快的方法来构建他们的系统。但是如果你有一个非营利性的项目，你可以试着自己构建一些东西。例如，您可以使用JQuery或Dojo作为ajax工具包，如果您正在编写web应用程序，并且您想要设置一些ajax功能，则手动构建这些功能将需要时间:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5410430|但在使用第三方库时也必须小心，您必须信任它们，因为它们可能包含恶意代码，或者它们编写得非常糟糕，可能会让您头疼。|5410431|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Don't forget that the time is a big issue for writing all things by your hand, it is not that you cannot do that but the problem comes from your customers or company they always want to find the fastest way to build their system. But if you have a non-profit project you can try building things by yourself. For e.g you can use JQuery or Dojo as your ajax toolkit if you are writing web applications and you want to set some ajax functionality, it will take time to build those things by your hand :)

But you also must be careful when using a third-party libraries, you must trust them because they can contain malicious code, or they are very poorly written and can cause you headache.

blocks|key|3153903|text|这个问题没有一个明确的答案，因为就像软件开发中的任何其他事情一样，它取决于情况。我要说的是，如果以下三点是真的，那么你就不应该考虑自己去做……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3153904|如果它不是您的业务或专业知识的核心，请使用|3153905|。|ordered-list-item|3153906|如果是其他人为您编写的，并且在广泛使用的|3153907|中使用，则它可以满足您的需求，或者可以进行扩展以相当容易地满足您的要求。|3153908|3153909|3153910|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|S|8|@]|9|@]|A|$]]|$1|K|3|-4|5|F|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

There is not a definitive answer to this question because just like anything else in software development it depends on the situation. I would say that if the following 3 items are true than you shouldn't think about doing it yourself...

<ol>
<li>If it's not core to your business or expertise.</li>
<li>If someone else has written it for you and it is being used in widespread communities.</li>
<li>If it meets your needs and requirements or it can be extended to meet your requirements fairly easily.</li>
</ol>

blocks|key|829979|text|“哪些功能应该始终是第三方的？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|829980|没有。在讨论本质上的工程决策时，总是有例外或特殊情况来否决“总是”的惊人用法。|829981|此外，转向第三方的决定几乎永远不应该基于给定的“功能”。没有这样一个完美的库，你永远不需要去其他任何地方来实现这种类型的功能。|829982|选择第三方是应该基于以下因素做出的决定|829983|使用第三方的成本vs.根据最后期限所需的时间(例如，它可能在内部更便宜，但您的开发时间表可能不允许集成、调试、维护和升级路径的regardless)|829984|Ease+-它可能是您可以开发的东西将“完成这项工作，但勉强”在内部vs.没有更多的钱为一些将照顾您多年|unordered-list-item|829985|
|829986|829987|829988|/成本的测试和证明-安全包是出了名的难以测试良好|829989|829990|然而。有些事情真的很难相信呆在家里会更好。例如，您可以编写OpenGL和DirectX的竞争对手，在某些应用程序(科学计算等)中，有充分的理由考虑这样的路径。但一般来说，你不会想到它的。即使它是“免费的”，它仍然是第三方的依赖，你可能会因为一个只影响你如何使用这些图形语言的bug而陷入困境。|829991|换句话说，存在一些令人难以置信的复杂或难以证明/测试的东西，这些东西几乎总是应该交给第三方。安全性是另一个问题。不要写你自己的散列算法，除非你1)确实疯了，2)至少有3个很好的商业理由这样做。|829992|但是“什么功能应该始终是第三方的？”没有。总会有例外的。|829993|-Adam|829994|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|-4|5|L|7|1A|8|@]|9|@]|A|$]]|$1|P|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1C|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1F|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1H|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|12|$]]

"What functionality should always be third-party?"

None. there is always an exception or special case to overrule the egregious use of "always" when discussing an essentially engineering decision.

Further, the decision to go third party should almost never be made on basis of a given "functionality." There is no such thing as such a perfect library that you never need go anywhere else for that type of functionality.

Going third party is a decision that should be made based on

<ul>
<li>Cost of going third party vs cost of doing it in house</li>
<li>Development time required placed against deadlines (ie, it might be cheaper inhouse, but your development timeline might not allow it regardless)</li>
<li>Ease of integration, debugging, maintenance, upgrade paths - it may be that you can develop something that will "do the job, but barely" inhouse vs not much more money for something that will take care of you for years to come</li>
<li>Ease/cost of testing and proving - security packages are notoriously difficult to test well</li>
</ul>

However. There are some things where it's really tough to believe that going in house is better. For instance, you can write a competitor to OpenGL and DirectX, and in certain applications (scientific computing, etc) there are good reasons for considering such a path. But in general you wouldn't dream of it. Even though it's "free" it's still a third party dependency, and you could end up on the skids because of a bug which only affects how you use these graphics languages.

In other words, some incredibly complex or hard to prove/test things exist which should almost always go to a third party. Security is another one. Don't write your own hashing algorithm unless you are 1) certifiably crazy and 2) have at least 3 excellent business reasons to do so.

But "What functionality should always be third-party?" None. There's always an exception.

-Adam

blocks|key|3154207|text|核心业务之外的任何东西都是第三方解决方案的理想选择。您希望将开发时间花在创建独特的核心功能上，并且不能以低成本的方式购买和使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3154208|例如，让我们看看web+gridview控件。你能自己开发和扩展一个网格视图吗？当然可以，但是开发、编码和测试网格视图将花费X个时间和资源，您可以将其转化为美元。现在，您已将支持、维护和错误修复的重复成本考虑在内。|3154209|现在让我们使用我记得在一些杂志上读到的任意数量，关于美国开发人员平均每小时40美元的收入，包括他们的福利。有完整的web控制套件可供选择，每个开发人员许可证大约800美元。如果您的开发人员在这个控件上总共花费了超过25个小时，那么您可能已经购买了整个套件，并花费了5个小时进行集成和测试。|3154210|现在希望我没有弄得太糊涂，但一般的要点是，如果你能从自己那里买到它，它可能会节省时间和金钱，而不是专注于你不能从自己身上得到的东西，这些东西通常是你的钱制造者。|3154211|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Anything that is outside your core business is a good candidate for third party solutions. You want to spend your development time creating that core functionality that is unique(ish) and can not be purchased and used in a cost effective manor. 

For example, lets look at web gridview control. Can you develop and extend a gridview yourself? Sure you can, but to develop, code, and test you grid view is going to take X amount of time and resources, which you can translate in to dollars. Now you have factor in reoccurring costs for support, maintenance, and bug fixes. 

Now lets use the arbitrary amount I remember reading in some mag about the average US developer making $40 per hour including their benefits. There are whole web control suites available for around another approximated $800 per developer license. If your developer spends more than say 25 hours total on this one control, you could have purchased a whole suite and spent 5 hours integrating and testing. 

Now hopefully I didn't get too confusing there, but the general gist is if you can buy it off the self it will probably save time and money, and instead focus on things you can't get off the self which are usually your money makers.

blocks|key|3999807|text|如果您可以以比构建成本更低的价格购买它，并且购买的功能满足您的业务需求，那么就购买它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3999808|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you can buy it cheaper than you can build it, and the bought functionality meets your business requirements, then buy it.

blocks|key|830064|text|我要说的是，对于编写样板代码，或者几乎每次都被复制和粘贴的冗余代码，应该通过库来完成。对我来说，验证代码几乎总是让我犯愚蠢的错误，因为它很无聊。Spring.NET在这方面令人惊叹。我很高兴我的老板鼓励我尝试一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|830065|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'd say for writing boiler plate code, or redundant code which is copy and paste almost every time should be done through a library. For me, validation code almost always has me making stupid mistakes, because it's boring. Spring.NET is amazing for this. I'm so glad my boss encouraged me to try it.

blocks|key|3154330|text|这个问题与问题相反:你应该创建什么软件？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3154331|这显然是愚蠢的。|3154332|因为两者都没有唯一的答案，这取决于你的业务需求。你需要为整个互联网建立一个更好的搜索引擎吗？几乎可以肯定不会。但如果你是90年代末的谷歌，你就会这么做。第三方和第一方只是你在哪个办公室工作的问题，每个第三方都是他们自己的第一方。|3154333|你所需要的一切都足够好了:使用shelf.之外的东西|3154334|要么你会创造一些低质量的东西，要么你会把钱和精力浪费在无关紧要的东西上，或者两者兼而有之。|3154335|3154336|If这是你业务的基础:+build+it+yourself.|unordered-list-item|offset|length|style|BOLD|3154337|3154338|如果你可以创造出更好的东西，并且你可以在更好的东西上建立起一家企业，那么就去做吧！|3154339|entityMap^0|0|0|0|0|0|0|0|U|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|12|8|@$N|13|O|14|P|Q]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

This question is the inverse of the question: what software should you create?

Which is obviously silly.

For both there is no one answer, it depends on the needs of your business. Do you need to build a better search engine for the entire internet? Almost certainly not. But if you are Google in the late 90s, you do. 3rd vs. 1st party is just a matter of which office you work in, every 3rd party is a 1st party to themselves.

<ul>
<li>If all you need is good enough: use something off the shelf.</li>
</ul>

Either you'll create something lower quality or you'll waste money and effort on something that doesn't matter that much, or both.

<ul>
<li>If it's the foundation of your business: build it yourself.</li>
</ul>

If you can build something better, and you can build a business out of that better thing, then do!

blocks|key|3154498|text|看起来你有你需要的所有答案，但我只想在这里和其他人一起提出我的观点。客户付钱让你制作专门为他们工作的应用程序，这通常就是他们去找你的原因；他们需要的东西在市场上的任何其他产品中都找不到。因此，您的重点应该是开发他们需要的特定部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3154499|毫无疑问，您的应用程序还需要做其他事情。也许它需要连接到数据库，或者加密某些线路。这就是第三方库发挥作用的地方。你不想浪费时间为一个数据库写一个新的驱动程序，或者一个可能有你没有时间测试的漏洞的新加密方案。您想要使用已经存在的，并且经过广泛测试和优化的工具。|3154500|记住，你完成得越快，他们支付的费用就越少。这让他们很高兴，并希望回到你身边。这也意味着你赚得更多，因为即使他们支付的更少，你也可以从事更多的项目，这意味着更多的钱。|3154501|总之，您应该在其他模块中依赖第三方库。|3154502|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

seems you have all the answers you need, but i would just like to throw my opinion in here along with everyone else's. clients pay you to make applications that work specifically for them, and that's usually why they go to you; something they need isn't found in any other product on the market. thus, your focus should be on developing that specific part they need. 

undoubtedly your application will need to do other things as well. maybe it will need to connect to a database, or encrypt certain lines. this is where third-party libraries come into play. you don't want to waste time writing a new driver for a database, or a new encryption scheme that might have holes you don't have time to test. you want to use the ones that already exist, and have been extensively tested and optimized.

remember, the faster you finish, the less they will have to pay. this makes them happy and want to come back to you. this also means you make more because even though they pay less, you can work on more projects, which means more money.

in conclusion, you should rely on third-party libraries in miscellaneous modules.

What prompts my question is <a href="http://www.codinghorror.com/blog/archives/001172.html" rel="nofollow noreferrer">this post from Jeff Atwood</a>, and <a href="http://www.25hoursaday.com/weblog/2008/08/31/DevelopersUsingLibrariesIsNotASignOfWeakness.aspx" rel="nofollow noreferrer">this post</a> from Dare Obasanjo. It seems to me that there might be at least a few areas where third-party functionality is a better idea than custom code.

For example, should logging always be third-party? How about encryption? Or search?

I'm looking forward to everyone's feedback on this.

Edit: This question assumes that logging, encryption, and/or search isn't your core business.

What functionality should always be third-party?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

引发我问题的是来自Dare Obasanjo的和。在我看来，至少在某些领域，第三方功能比自定义代码更好。例如，日志记录应该始终是第三方的吗？加密怎么样？或者搜索？我期待着每个人对此的反馈。编辑:此问题假设日志记录、加密和/或搜索不是您的核心业务。

问哪些功能应该始终是第三方的？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问哪些功能应该始终是第三方的？EN