Geek Answers Handbook

Best Practices for Creating Web Services

In the introduction, I am new to web development. I am considering creating a basic set of RESTful web services around a valuable document library (CRUD source capabilities). In doing so, I theoretically create a completely reusable and scalable server that will be used by unforeseen applications in the future.

My question focuses on best practice for this. In my initial requirement, I also created a unique interface. Can I make the front and back completely separate projects to improve reuse. This would increase overhead.

Looking at using a stack of GWT, Restlet, and Java EE technologies, if that affects configuration at all.

+5
source share
5 answers

The most important thing is to create a pure Java API - regardless of the REST, RMI, or any other protocol that you want to use. With a pure Java API, you can support any access method.

If you have no precedent for these other access methods, do not create them now. You can build it when you need it.

The easiest interface to add is the web interface, where your web application runs in the same JVM as your main API. I would do it if it works for your use case. Creating a separate console application that accesses your core API through the REST protocol (or something else) works a lot more.

+2

REST: . REST.

+1

REST, RestyGWT, GWT- RPC , JSON.

JSON REST GWT-RPC , mashups .

+1

, GWT-RPC REST, , GWT . .

, , , , REST API , REST .

gwt-rest .

0

GWT, . , . , .

Also, given that you are new to web development, I don’t think you should count on creating a completely redesigned backend. You will learn a lot of things when you go. I think that flexible coders recommend using an iterative approach (a) to get a small aspect of the work, and then (b) refactoring it to make it beautiful.

0
source

More articles:


All Articles