Steve, Wayne, and I were talking about serves and direction. We were talking about getting things going with Newtek with the new VPS and clustering options. We are somewhat putting AWS stuff on hold. We have been over there for six plus months and still having some issues and running into small little barriers of sorts. We have had great success with Newtek and want to keep that ball moving forward.

One of the main topics of the day was the data 0 box. It is currently our oldest box and plays a pivotal role. It is somewhat of the gateway for the rest of the system. We are going to be trying to change that and get all of the normal companies that need production level capacity to other servers. Basically, we are going to be splitting up the corporations (worlds or business entities) on that server into a couple of new spots. It should help things go faster and lessen the load on the actual gateway that data 0 plays (as far as a redirect or doorway type application).

Here are some of our other notes. Lots of good chats and talks.

- Lewis and Clark expeditions and mapping things out and figuring out what to do and where to go next. This is part of our explorations that are needed in the digital realm.

- Splitting up databases in to different datasources (where are things pointed) and also the structure of the data. We talked about certain tables that are independent, certain tables that need to stay as shared or master data, and other tables that are for sure corp-specific or based on a per world level. Interesting conversation. Going back to the older world building ideas - cluster database vs solar system databases.

- Wayne was mentioning that he would like to work with Alan on splitting things up between the database and different datasources. That could be really cool. Wayne was also mentioning about using the DAO's (data access objects) and having that be part of splitting up the databases. As a side note, if we create new databases and datasources for each company, we would potentially be duplicating a lot of data. It may be faster, but we need to look at what that extra duplication would cost as far as connections, storage, and even eventual clean-up. In short, moving to the DAO model vs duplicating existing databases.

- We are really trying to move more towards the adilas community funded projects... similar to how the open source software and community operate and flow. If someone really wants something big, they need to make some resources available (time, money, ideas, people, etc.).

- We talked about selling the data storage and processing services. In a way, we could say, our system or software is free, you just pay for the services that you need to support that. Those could be setup, hosting, storage, processing, custom code, marketing, training, consulting, design, etc.

- We briefly talked about owning our own hardware cluster there at Newtek. It was on Steve's list to talk about. Wayne chimed in and recommended that we not go in that direction. He explained that if we stay on Newtek's hardware clusters, they have a reason to keep upgrading and maintaining those clusters. If we ride on top of what they are doing (their products and services) we gain from all of their advancements. If we are on our own, we have to provide all of those upgrades and maintenance pieces. Great point and something to think about. Ideally, if we gain enough, we would be better off riding on top of these other products and services.

- We spent some time talking about the refresh rate and the replacement rage of hardware and who manages that.

- Stress testing on the servers - Finding server level breakpoints and stress and load testing on servers. We pointed Wayne to a number of bigger reports and processes. He will simulate those loads on some test data to see if we can find any stress points, breakpoints, and other info we can gain by load testing things. Wayne would like to work with some of the reps and consultants to find the pain points and going the daily grid and what works and what needs some more loving.