Full Stack Android Development

I am working on a project but don't really have spare time to complete. This is a full stack development. Requires 3 core components 1) Server side: There will be more than 1 servers, servers will communicate with each other by using RabbitMQ either shovel or federation(as servers are not located in the same datacenter) (please don't offer me anything if you've never worked on any AMQP, I don't like sockets or similar ways of "missing implementations for the real world"). The idea of having more than one server is reliability. Servers will have a database and all servers need to synchronize databases when there is an insert/update. Don't worry about the details of the database I would only require 3-4 simple tables. I'd prefer SQLite for that as it is only a file and does not require any installation. The other part of server side is Android-Server communication, Android client should be able to get all available server addresses so that any disconnection must be handled by the other server (you don't have to worry about this part, simply if ack is not received you can have a pop up saying it is disconnected and expect user to do the task again). The client will log in into this server, and server will have database wrappers to be able to write/read data from database(clients will not directly connect to the database). This client-server communication will also be done by RabbitMQ, however must be separated from the server-server communication. The last part is HTTP server. The same username password used for Android client will be used to log in. This will be used for a browser client to view and edit the database. This server must be written in Java and all external libraries must be working fine with Linux and Windows. I have cross-compatiable libraries for SQLite and HTTP Server. I can send it if necessary. 2) Android client The client will have 2 roles(determined by the account), therefore they will have different Activities. Again the role determination is done at the server side, nothing will be determined by the client. The client must be written for tablets, not for phones. 3) HTTP As mentioned above will be very basic, just log in screen and view/modify some database fields(determined by the account) Please contact me if you have questions or would like to learn more about it.