Wayne, John, Alan, and Brandon on a server type meeting. Talking about advanced API options, swagger docs, AWS (amazon web services), and other options. Leaning towards AWS options to allow for high functionality and high demand sites and API's. The talks even got into some costing models and other topics.

Wayne was proposing that we see what the primary functionality is and what is needed and then just do that first. Kinda like a trial run and a virtual prototype.

Steve joined us via phone call. Light discussions about traffic and load balancing. Talking about 10,000 instances and what would that take. Performance and reliability in those high traffic sites. Lots of unknowns and questions.

Alan was talking about separating transactional data and the reporting side of things. Figure out which areas need more flexibility and which areas need high availability (load and traffic). Clustering servers and what would that take?

Bring in more people or do an all hands on deck call for our current developers? Talking about options. We were also talking about documentation, questions, contracts, requirements, stats, matrixes, usage, scalability, etc. Still a lot of unknowns... more information will need to keep coming in for us to make better decisions. Another big question is how big do you want to be?

Question from Alan - What about supporting tons of other developers and their API coding languages? Also, are we talking about duplicating all of adilas or just a few specific API sockets and pushing all of the new traffic over there? It goes back to pain points and priorities.

There was also some talks about co-branding things and even creating different entities as needed. These are some of the other options that we are talking about.