Saturday, August 14, 2010
I Just Realized, GAE has no SQL Injection
Wahoo, GAE has no SQL injection to worry about. I see some HTML/javascript cleaning to be done on vars being sent to the server, but one things for sure, GAE rocks.
Make GAE Work For Me
Switching from a relational database to consistent distributed database is so challenging for me. I'm having a hard time with recursive relation ships. I'm having a hard time with one to many joins. I'm having a hard time thinking of storing data redundantly. Stink on a duck, this is hard. Although having said that, I need to change to a distributed model so I can scale. I suppose I'll wait for a nice join system to appear on the scene, but the complexity of it may take a while for them to work that out.
All in all, I'm working on my own join of my datasets. After I consolidate my recursive ownerships, I plan to build my own join. If I can't have a join, I'll build my own. What's driving me nutz now, is that I'll have twice as much times the indexes that are created for both sets. But hopefully data storage is cheap, b/c I have to make a decision on some way to go, and that way better lead to getting GoneVertical online this year.
I think most of my problem is switching gears to consistent database system. I'm not sure entirely yet what the pros and cons are because I don't have enough experience int he consistent db JDO storage field. Hopefully soon, as I bring my data online, I can see how its going to work for me and be able to scale it faster.
At least something is for sure, I'm slowing moving towards my goal at a slugs pace.
Brandon
All in all, I'm working on my own join of my datasets. After I consolidate my recursive ownerships, I plan to build my own join. If I can't have a join, I'll build my own. What's driving me nutz now, is that I'll have twice as much times the indexes that are created for both sets. But hopefully data storage is cheap, b/c I have to make a decision on some way to go, and that way better lead to getting GoneVertical online this year.
I think most of my problem is switching gears to consistent database system. I'm not sure entirely yet what the pros and cons are because I don't have enough experience int he consistent db JDO storage field. Hopefully soon, as I bring my data online, I can see how its going to work for me and be able to scale it faster.
At least something is for sure, I'm slowing moving towards my goal at a slugs pace.
Brandon
Sunday, August 8, 2010
Rewriting My App to GAE is painful.
Right now I am thinking re-writing an application is really challenging. Especially when the database engine is really different and somewhat abstract or at least it is in the beginning. I find my self second guessing my self all the time wondering if my core-engine I created for Gonevertical.com was the right thing to do. Trying to fit data into a dynamic spec has been quite the challenge combined with the distributed data store.
While trying to preserve the structure to limit my first phase re-write only to push the app to google app engine has been painful. Working in abstractland is really hard on the brain at times, because I've only been able to get short focus times on the weekend in between family time, incrementing my progress on the small scale.
I get frustrated with my progress and the timeline I'd like to launch, hopefully before the new year. Although, I have several systems to cover yet and not sure I can make it. At this point I figure it could take up to 50 days to launch the new version, and that time is built only on the weekends and some week nights if I can fit them in.
Some thoughts as I struggle to launch our next version,
Brandon
While trying to preserve the structure to limit my first phase re-write only to push the app to google app engine has been painful. Working in abstractland is really hard on the brain at times, because I've only been able to get short focus times on the weekend in between family time, incrementing my progress on the small scale.
I get frustrated with my progress and the timeline I'd like to launch, hopefully before the new year. Although, I have several systems to cover yet and not sure I can make it. At this point I figure it could take up to 50 days to launch the new version, and that time is built only on the weekends and some week nights if I can fit them in.
Some thoughts as I struggle to launch our next version,
Brandon
Subscribe to:
Posts (Atom)
