tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/4249-struggling-with-services-and-best-practicesRobotlegs: Discussion 2013-11-15T11:45:49Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/297522972013-11-04T16:41:28Z2013-11-04T16:41:28ZStruggling with Services and Best Practices<div><p>I'm sorry that you haven't got an answer until now. As for
myself, I've had a prolonged weekend away from my computer.</p>
<p>I don't know if I can add anything new to what has been
discussed so many times on this forum about Services and Models
over the past years.<br>
As you are well aware, very large Service APIs are not good. You
want to remedy that, but at the same time you're afraid you'll end
up having too many separate Services ;)</p>
<p>What is your Service supposed to do, what kind of data source is
it accessing (file system, web services, LSO...)? Why are there so
many different methods? Is it a 3rd -party API?<br>
Is your application having lots of different functional areas, that
require accessing different data sources, or do they have a lot in
common, like some SCRUD operations?</p>
<p>First, see if [1] Shaun's or [2] Stray's answers are of any help
to you, and we can then continue the discussion:</p>
<p>[1] <a href=
"http://knowledge.robotlegs.org/discussions/robotlegs-2/38-service-with-a-large-api#comment_17269563">
http://knowledge.robotlegs.org/discussions/robotlegs-2/38-service-w...</a></p>
<p>[2] <a href=
"http://knowledge.robotlegs.org/discussions/questions/327-one-service-for-many-actions#comment_3395312">
http://knowledge.robotlegs.org/discussions/questions/327-one-servic...</a></p></div>Ondina D.F.tag:robotlegs.tenderapp.com,2009-10-18:Comment/297522972013-11-04T20:27:18Z2013-11-04T20:27:18ZStruggling with Services and Best Practices<div><p>Thanks! Both of those articles are very helpful.</p></div>hays.clark