meeting with wayne on 12/29/20

trying to fill in the gaps (knowledge and/or know how)

how DNS stuff works
	- buy a domain name - ex: adilas.biz
	- each domain has a number of records - where is is pointed and where is it hosted
	- we bougth the domains through doster.com - called a registra (list of domain names)
	- we were using our own DNS (domain name server) records on adilas servers
	- we had the DNS server stacked on top of the normal web servers (2 in 1 type model)
	- we are, and have been, moving those DNS records off the main serves and having an outside party help control the domain routing
	- usually DNS stuff is super quick
	- DNS reroutes things and points to IP addresses behind the scenes - lots of IP address flipping
	- Cory had a question... about the cart (stored in session memory)
	- one of our biggest variables is how the users (our clients) use the system.
		- time of day
		- number of records
		- dependence on outside resources, libraries, 3rd parties
		- what are they doing... that changes so quickly

old www.adilasdata7.biz >> new data7.adilas.biz
	- a couple of vars
	- we changed domain names
	- the database is no longer on the same box
	- we could check the ColdFusion settings
	- the new domain name goes through Cloud Flare

we don't know how to fix it...

tech support - Shari O. and Cory
	- how to contact support
	- what are the server names
	- real data 20 - aka old data 2, is actually under data 4 in the system
	- we need to call and ask for servers to be rebooted or services to be reset

security vs customer service - good security creates good customer service
	- Cloud Flare as a 3rd party solution
	- errors and limits
		- timeouts (100 seconds)
	- hacking
	- poor coding practices
	- balance between the two
	- dammed if we do, dammed if we don't - catch 22
	- performance suffers
	- what are the clients requesting? amount of data? time ranges?
	- the reason we brought on Cloud Flare was data 0 was down for hours and hours.
		- we had hackers... attacks, news and updates, etc. - totally down
	- there was a reason we moved servers from Newtek to Hostek
	- we have been responding... none of our changes were made in a vacume (dynamic)

old - call first... just take care of it

new ish - let wayne know - see what's wrong
	- if he responds... we are golden
	- if he doesn't... we panic
		- they (tech support) would love some communication
		- if not, we roll to the next level
		- we can use his google voice number - sometimes we do have a delay - 208-991-3205 (google voice)
		- his direct line is +351-915-621-296 (in portugal) - to get the + sign, hold down the 0 key.
		- wayne prefers a call, even if it is late where he is... he is 7 hours different in portugal
		- this is the bat phone at Hostek number - 800-329-2166
		- we need to use Hostek more - they know ColdFusion and they know servers

clients want reliability

wayne is trying to solve the underlying problems
	- watching slow pages and queries
	- more memory
	- other settings and tweaks

glad that John and Wayne are working together. That is awesome. Hoping to get John some good training in Jan 2021.

cory wants to get a protocol or a procedure in place
	- they don't like to do a full reset or full reboot unless they really need to

To recode would be huge... soooooo many things would need to be updated and recoded

it takes time for us to make changes and get things done and changed

how do we respond quicker?

wayne is looking at the logs and has a good bead on what he thinks that hackers are wanting to do
	- actively looking and trying to protect things

there was some talks about doing testing and simulation for load testing and trying to break and/or push our servers using a predictable load on the servers - each of our live servers are so differnet... we would have to almost create a syntehic load to help do some load testing (cardio workout for a server)
	- wayne needs someone to help him know what to do (the processes) and then someone to help him navigate the server. once he catches that... he could simulate those processes and do his locus swarms (tons of processes and load testing).
	- it might be good to get cory, john, and wayne working together to run these stress tests
	- wayne could do it all by himself, but he is not an adilas power user... he needs that part to be provided through a real power user who uses the system
	- they were talking about doing a duplicate of data 7 and then running some load testing on the duplicate... we need the same data, the same usage, etc.

adilas is admitting that we need to move more towards aggregated data in certain areas... currently, all action, queries, and reporting is based on transactional data - which is ever growing

there are some known tables (within the database - like po/invoice line items) that are huge and growing. We use those tables over and over again for sales, inventory counts, and financials - we keep going to the same tables over and over again - lots of traffic. Good data, but it needs to be aggregated and summed up to make a real differnece.

we are at the end of the year... things should open up after the first of the year - for all parties.