Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 11/2/2018 10:10 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4155
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 11/26/2018 8:00 am
End Date/Time: 11/26/2018 1:15 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

- Tons of emails and light tech support from things over the Thanksgiving weekend.

- Brandon and Steve talking about updates on people - we were talking about Shannon, Russell, and Dave Forbis.

- Alan popped in and had some questions about his new projects. He is working on discounts on my cart favorite buttons.

- We lightly talked about vertical (business verticals or industry-specific) templates and settings. Make it easy to cater to specific verticals.

- Talking about system stats and storing that info in a daily watcher or feeder type table. We also talked about queued back end services that run on daily routines. We also talked about pulling reports and monitoring growth and changes.

- We were also talking about "rules" or standards per vertical (industry). Each industry is different, and thus may need some general rules based on the type of industry that they are. Basing the pricing off of processing and storage vs charging for the code. Some users may or may not be using certain features and/or modules. This discussion ended up going into questions about what do we want to do with the adilas databases (make it bigger and better or break it up into small faster pieces). This is still an active discussion and we are trying to gather pros and cons of both.

- Alan was talking about vertical and horizontal scaling - add more and more servers (distributed or cluster model) vs single server and up the capacity and resources. This lead into a small discussion on back-ups, redundancy, and disaster recovery options. Currently, we are doing somewhat of a modified horizontal scaling method.

- Steve had some questions about the API socket level and what that load may be and/or take?

- Alan had some ideas on risk mitigation and how to help our clients even do their own risk mitigation processes. Lots of talk about what are the vulnerabilities and how do you treat, track, and deal with those vulnerabilities. It always tends to come back to an analysis of what is the threat and how much do I care, need, want, and/or require? Talks about server up time and reliability. What maters most and what are we willing to pay for and/or spend?

- We would love to show all of the corporations (virtual worlds) what their stats are and what we (as adilas) are carrying and helping them out with. That helps us show a benefit and advantage for those who use adilas.

- We lightly talked about an offline adilas mode and allowing a user to use the main web system, if a problem, they could use a local copy, and then sync up things later on. This sounds awesome, but it could be a huge project and could be riddled with loop holes and gotcha's. Possible, but hard to tell what the real costs are and/or would be.

- The technology wave and what is here, coming, and already gone (outdated). We are constantly riding those waves and making decisions. Alan lives down there in Arizona and could maybe pop in and check things out with the actual server farm. We could even branch out and spread out our exposure to other server farms.

- We could update older servers to help with stability and up time. We could upgrade to using solid state drives, bigger processors, more RAM memory, and updated server and software packages. That could be a great upgrade for the time being. We also talked about optimizing our existing servers by tweaking settings and such (performance tuning).

- We may end up needing some new training on how to configure and upgrade the things that we need. This is just a possibility, but there is an upcoming ColdFusion summit convention coming up in April 9-10, in Washington, DC. Just looking at ideas and options. Our goal is to get the most out of what we can by either upgrading to the newest models and/or versions and getting the proper training needed to make it dance and sing. ColdFusion is allowing more and more scripting languages and is gaining some momentum.

- There was some small talk about upgrading from Windows servers to Linux servers. Wayne is the one that knows a lot there. Lots of possibilities.

- Some new shortcuts and getting up to speed. Alan was showing us some coding shortcuts. Params, is defined, and quick conditional processing. Things like a turnary operator (one line true or false if statement - switch), elvis operator (reference something and it is able to self-define if it doesn't exist but will use a real value if it exists - less breaking code for things that are undefined).

- There are many paths that we could take and would work. Let's make a plan and then work that plan.

- What we do is not easy. There are so many moving parts and pieces. As we build, we keep finding that it comes back down to more and more permissions and settings. Subs of subs. Eventually, it could become simple if you get enough sub pieces built into the mix. Kinda crazy.

- We are also seeing more and more needs for bulk tools and such.

- We are also seeing that people are really looking for a system that could do almost everything with both global tweaks (per business vertical) and also granular control (permissions, settings, etc.). Almost a wish list of sorts.

- As we get out, in the field, we may end up adding some icing here and there. Maybe even some icing per business vertical.

- On black box stuff - what if we had a list of what happens and/or what black box code is running? We may need to use some kind of technology to help us monitor and/or use what black box code that is out there. Maybe a way to notify our developers, consultants, and even our users what code they are using.

- Small concepts - creating an adilas fracture account - future concept once we get a few of the other pieces in place. This was an idea from Steve, clear back in 6/22/17. We would basically, allow the normal or classic adilas to keep going, and then start building out the adilas fracture accounts. Everything would be broken up into tiny modular controls but would also have bulk tools, templates, and industry specific defaults to help play the game. This subject could take up volumes, as far as other ideas and concepts that we would like to include. Super cool idea and future project.

- Steve would like to see us work on breaking out users from the systems... They, the user pools, exist and can interact as needed but they become their own entity - Imagine pools of professional (adilas community members and power users) users that could work for other companies as needed. Separate users and systems, even more than what they currently are. Steve has some good ideas on that. Kinda like a marketplace for features and functions as well as power users, employees, and people talent. Fun ideas.