维护API的成本 [英] Cost of maintaining a API

问题描述

你们中的任何人都有建立和维护产品API的经验。维护它是否便宜或昂贵？是否限制了进一步的开发？



我很乐意收到您对该主题的意见。

Do any of you guys have experience of building and maintaining a API to a product. Is it cheap or costly to maintain it? Does it restrict further development?

I would be happy to get your input on the topic.

推荐答案

取决于您的架构如何，它不一定非常昂贵。由于您的产品需要和设计变更以满足您的要求，因此维护API的成本将在很长一段时间内实现。然后，您可能不得不担心保持向后兼容性。



构建API有两个主要原因，1，允许第三方开发人员使用您的产品和功能，以实现自己的结果。或者2让您的内部开发人员更轻松。如果您推测API是前者，那么它可能会更加昂贵，因为您需要确保API的新版本不会破坏第三方开发人员，否则他们会生气。如果是晚些时候成本保持下降。您可以更好地控制内部开发人员的工作内容和方式。



构建API总是一个好主意，特别是如果它对您的开发人员有所帮助。应将常用功能集成到API中。您想要权衡的是，每当他们需要读取和写入文件，连接到数据库并获得10个以上必须维护的不同实现时，让内部开发人员为自己的功能发挥作用的成本，这需要花钱，或者你是否希望所有包装好，紧凑并保持在一个地方？然后弄清楚会花多少钱。



在整个API中设计和建造一口井可能会在短期内花费更多，但你会意识到长期的节省。只要您支持API的产品没有大幅改变，那么支持API的成本就可以很好地平衡并保持低水平。那次谈话就是这样的，



我们所有的开发人员都希望使用这个功能吗？ - 是的，添加到API或维护此工件会更具成本效益吗？



如果两者的答案都是肯定的，那么你''重新进入维护API的位置，在初始设计中执行黑客工作将导致您不得不经常添加少量修改和维护！做好工作并经过充分测试，虽然在将其发布给开发团队时设计的API非常有用，这将极大地帮助您降低成本。但这需要预先进行强有力的投资。



所以为了回答你的问题，YE推进了发展。如果做得对，维护起来可能很便宜，但如果做得好，很多软件维护起来都很便宜。您拥有的好处是，您的团队可以在没有API的情况下继续使用，因为您还没有API。所以没有急于上市，因为它是一个内部产品，你有时间做得很好。

It doesn''t have to be costly, depending on how your architecture. The costs of maintaining an API are realized over a long time, as your products needs & design change to match your requirements. Then you potentially have to worry about maintaining backwards compatibility.

There''s 2 main reasons to build an API, 1, allow 3rd party developers to use your product and features, to achieve their own result. Or 2 make lives easier on your in house developers. If you reasoning for the API is the former, then it can be significantly more expensive, as you need to ensure that new versions to your API don''t break 3rd party developers, otherwise they get angry. If is the later then costs stay down. You have more control over what & how your in house developers do.

Building an API is always a good idea especially if it''s to be of assistance to your developers. Common functionality should be rolled into an API. What you want to weigh is the cost of having your in house developers role their own features every time they need to read & write to a file,connect to a database and getting 10+ different implementations that all separately have to maintained, which costs money, or do you want that all wrapped up nice and compact and maintained in 1 place? Then figure out what''s going to cost you more.

Designing and building a well throughout API may cost you more in the short term but you''re going to realize the savings over the long term. As long as your product that the API is supporting doesn''t change drastically then the costs of supporting the API can be well balanced out and kept low. That conversation goes something like this,

"Is this functionality all our developers are going to want to use?" - Yes, & "Will it be more cost effective to add to an API or maintain this artifact?"

If the answer to both is yes, then you''re into a position of maintaining the API, doing a hack job at the initial design will cause you to have to constantly add little modifications, and maintenance, frequently! Doing a good job and having a well tested, though tout designed API by the time you release it to your dev team will help tremendously and keep your costs down. But this requires a strong investment up front.

So to answer your questions, YEs it advances development. It can be cheap to maintain if it''s done right, but lots of software can be cheap to maintain if done right. The benefit that you have, is that your team can continue to get by without an API, because you don''t have one yet. SO there isn''t a huge rush to market as it''s an internal product and you''ve got time to do an excellent job on it.

这篇关于维护API的成本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！