We Keep Coding

Can google's firebase(Real-time database) work with a java desktop application? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I want to communicate my android application with java desktop application using real time database (Firebase).

It is possible to create a Java desktop application that uses the Firebase Admin SDK for accessing the database and other features. The syntax is similar to what is used in Android apps.
But note that this uses the Admin SDK, which (as its name implies) gives users full, administrative access to the back-end. Depending on your use-case, that may not be what you want.
An alternative would be to have your JavaFX application talk to the Firebase Database's REST API, which is documented here: https://firebase.google.com/docs/database/rest/start
Also see:
Can google's firebase work with a java desktop application?.
Using Firebase Admin in a Java desktop application (using Eclipse)

Yes you can connect it.In firebase, database is stored in JSON format and you can communicate using java networking api like java.net and connect to firebase. Also, in your project, you need to use JSON api's inorder to process/manipulate json data from firebase.

ESB backed database [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Background:
I work in a organisation, uses hundreds of software systems, we identify which system owns which category of data, then carefully select the data we want to expose to the other systems. then pull them into a single Oracle database.AKA master data.
then each system read the status of the other system through this shared database pattern.
Problem:
access control, data handling, and lack of event notification, logic routing caused us lots of time and effort. We want to add a ESB layer in front of the
Potential Solution:
we are looking at SOA at moment, in specific Enterprise Service Bus Pattern.
we aware there are options like Camel, Mule and ServceMix. But I wander is there any resource, can assists our implementation?
is there any project been done the same way, e.g ESB fronting a Oracle database access?

I don't think you'll find much in this strict sense. ESB is basically made for transferring messages between enterprise services. A DB is not an enterprise service. In this case you'd need processing beans that handle your specific need.
What you could do, however, is to put a service in front of your DB. This service could then expose the DB in some format. For example, SOAP over JMS seems fitted to your use case. SOAP can handle security and access, JMS gives you asynchrousness and exactly-once delivery guarantee, which will be needed if working with a DB. ESB frameworks can handle JMS and SOAP very well.
So instead of looking for a "ESB backed database", as you called it, this service may be something that you can look for on the market, and then you can route client services by using an ESB, which makes sense.

Can you give me an advice about MVC client-server? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm going to create a desktop application (Swing) using the MVC. It will be chat and i have some questions. Which classes should be located on client? (View - its logical) Model? Controller? or both classes should be on the server side?
And which classes have to process my database?

If you are planning to have server-client and database access, this sounds like a typical 3-tier distributed system.
Database - represented as DBMS and located potentially on a separate machine. This should provide easy API for queries and updates from the server.
Server - this is where Model is located, again potentially on a different machine than database. Server however has means of working with the database, ideally via the aforementioned API.
Client - contains View and Controller. View is essentially the UI aspect of the Model located on the server. Controller processes user interaction and sends to the server in the processed (clean) form that the server can understand. This is done to reduce server load. The client has no means of accessing the database directly.
If it's all the same to you, I'd recommend to have a look at JavaFX, its MVC is much easier to implement and just plain simple to work with

How to create website using java [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have created a web page which has a form using HTML. I validate the entries made by the user using javascript, and then I read the data entered using doPost method of HttpServlet. Now, I want to store this data in a database. How do I proceed? What new things should I learn? Where does JSP and JDBC SQL come into picture? I am a newbie and trying to learn and implement.

Now I want to store this data in a database. How do I proceed?
You need to learn JDBC, it's an API which provides methods to communicate with the database. SQL [Structure Query Language] is a language which is used to communicate with the database, you write your queries in SQL to extract & insert data to & fro from db. The best resource to start with SQL in opinion would be this.
JSP forms the view of the application. Each thing has its respective role.
Check out the image

This question has some good answers as to how to go about learning Java based web development.
Either way, you have to start with Servlets and as for JSP, architecturally, JSP may be viewed as a high-level abstraction of Java servlets. JSPs are translated into servlets at runtime.
Then and only then move on to web frameworks. This compares different Java web frameworks out there. My personal preference is Spring MVC, it's also the most popular.
Learn what an ORM does and then move on to Hibernate which is an ORM for Java..

How to pass data from server to android app: REST vs Sockets [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'am writing an android app that needs some data from the server. I am also writing the server side in Java.
What is the best way to pass data from the server to the android device: with REST or Sockets (like Kryonet)?
In what format: XML/JSON (for REST) or plain Java objects?
Thanks in advance.

"Best" is very subjective, I think a very good way to communicate with a RESTful api is via Square's Retrofit library, which can be found here:
http://square.github.io/retrofit/
There is also Volley from Google,
http://developer.android.com/training/volley/index.html

Agree with nPn, "Best" depends on lot of app and user considerations. That said,
REST is preferred as it is most widely used and you have access to stable and optimized client libraries. Most of the these libraries support all kinds of use-cases and customizations. Web Sockets are well suited for real time or live content. If you have a different use-case , REST is strongly recommended.
With Android, JSON is well supported. There is a core JSON API included with Android that you can use without any client libraries. XML can be helpful if you plan to expose your APIs for public consumption (some platforms eg: JAVA, windows have strong XML legacy).
REST + JSON seems to be most commonly used combination in recent times, and lot of client libraries usually enable this use-case.