The Java deployment world is plagued with infra issues! Things we need to take care of:
- Shell accesses
- File System Storage
- Indexes corrupting and the list goes on…
So after my failed attempt to understand/decipher CORS issues on the AWS platform, I fortunately stumbled on google-cloud! And it is one hell of a bouquet of services for us petty and dev-ops-complaining Java folks!
So churn out a bitnami tomcat instance and you get the feel of the aws thing. For over a month now my google cloud app was(still is) talking to the mysql instance on aws, before that starts to drain my mini wallet, time to configure a mysql instance on google-cloud. And here are the steps:
- Have access to the SSH into your google cloud instance working
- Create following script (/home/bitnami/mysql-init):
UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') WHERE User='root';
sudo /opt/bitnami/ctlscript.sh stop mysql
sudo /opt/bitnami/mysql/bin/mysqld_safe --defaults-file=/opt/bitnami/mysql/my.cnf --pid-file=/opt/bitnami/mysql/data/mysqld.pid --init-file=/home/bitnami/mysql-init 2> /dev/null &
sudo /opt/bitnami/ctlscript.sh restart mysql
- Remove the script in step 2.
So it turns out to get mysql talking on your bitnami instance you only need to reset the password.
Further to enable remote access do this in
Next to enable remote mysql access via workbench you need to enable firewall ports to allow connections for tcp 3306 for a specific ip on your google cloud instance.
And there you go, you have a lot powerful config, much like aws ready to be used, backed by google!!
Once upon a time there was a Q&A that happened as follows…
Q:So when can you say that your local dev environment is ready?
A:When you have run a comprehensive unit test, pre-existing or drafted yourself.
Q:What is a comprehensive unit test?
A:One that covers all major components of the architecture you are working on.
Q:What can be the major components of an architecture, one may be working on?
A:Layer Code, deployment, DB, Jndi context, orm context, 3rd party API context.
Q:What’s your point?
A:You environment ain’t ready until all your environments are not accessible from your box. The best way to ensure this is with a unit test and know thy environment!
Databases are one topic that I have never had a chance to get deeper insights.
I started JDBC’ing when later I was surprised to know that one could connect to the database using ‘C’.
I had not worked enough to feel the pain of iterating over ResultSet and writing insert/update scripts that virtually went outside the screen when I saw the onset of “Hibernate-Relational Persistence for Idiomatic Java”. I never liked the writing/seeing/understanding XML, but I had no choice but to Well Hmmm!
And with most of the time spent in Hibernate, I never felt its features were intuitive to that of Java(in no specific order).
- First and foremost in Java, Enum are first class citizens, in Hibernate, working with an Enum is not at all trivial.
- Using composite keys asks you to maintain a seperate object for it.
- Already there were two worlds of entities in Application(objects) and entities in DB(records), now to understand the two, one needed to know how Hibernate understands the two worlds.
For simple applications, Hibernate is way to work with, but with very large applications, I did not like the complexity that it brought in atleast two occasions, requiring extra time to keep the DB and the hbm files in sync.
It could be the incorrect way of not completely relying on hbm for schema generation, but because these applications had predefined schema’s, this was the only possible safe-path.
Issues with RDBMS:
- Cost of mapping conversion(second level cache’s are not enough!)
- Transactions duplicates Locking- In general.
Tired of looking at xml, and with the option to write an application for fun, I have the option to evaluate the usage of Object Oriented Database.
I had found atleast a dozen implementation of such software, at the end it came down to db4o and Perst. And here is the summary of them:
- Most commonly used OODBMS.
- Easy to learn.
- Supports intuitive Refactoring of persistent classes.
- Support for Projections is not available(could not find).
- Lazy initialization supported with default level of depth.
- Has GIS Dataset
- Fastest amongst all OODBMS.
- Cryptic creation of indices for faster search.
- Concept of Links for references pollutes domain.
- No fixed DTD for import/export feature for refactoring.
Both the products have the following in common:
- Support for Transactions.
- Zero mismatch between object and saved data.
- Confusing Licence!
At the end, I have to give in to db4o for simplicity and refactoring features.
And that’s where I would start looking at injecting it into the application.
Concerns about OODBMS:
- Not Yet widely used – I wonder why?
- Clustering – I do not need it.
- Backup – RDBMS or File?
- Optimization – Exotic feature than a requirement.
So I would look forward to working on the application on db4o and will update on the findings!