JibberJobber Speed Issues Update

JibberJobber Speed Issues Update Thanks for your patience as we work through some speed issues weve had for far too long. This has been very frustrating for my team, not to mention expensive. Just today I was reading an article on my local news site about hackers.  Theres been plenty of talk about hackers, whether its because of the password leaks because of hacks into LinkedIn, Yahoo, and the hundreds of other high profile sites/cases, or because of the hacker influence on the 2016 U.S. presidential elections. Hackers seems to be a far away thing, not really impacting our day-to-day life (thats arguable, I know).  But it has definitely impacted me, my developers, and my users, every single day. Just yesterday we had a pretty light day only a few thousand hacking attempts were made. Only a few thousand. It made our server slower, because instead of just serving our users, it had to address the hackers requests.  So, users write us and report that it takes 20 or 30 seconds for a page to load. That is ridiculous, and unacceptable. My team gets distracted because I say stop what you are doing and lets address this.  That means that what they are working on gets put on hold and JibberJobber evolves and improves slower than it should. This problem is frustrating and expensive. It is also demoralizing to everyone involved. We have a plan moving forward, though.  Its like Plan B, but really, Plan L or J.  Weve been working on this problem for years. I think this is the right plan, though.  We have a new server admin involved, and will be switching JibberJobber to Amazons hosting environment. That makes me nervous just typing it, only because when we first launched JibberJobber Amazon was having all kinds of reliability issues it just didnt seem ready to host our stuff yet. But I think its time.  Were moving forward on switching to Amazon, the pioneer and leader in cloud hosting. Inherent in that move should be always-the-best hardware, as well as anti-bad-guy software to keep the hacking down.  Those are two great benefits of the move. In addition, the new server admin will be working on finding and identifying any place that he can help, including speed optimization, security, and other stuff (contingency, code delivery,  and other things the developers will know about, but users typically wont see). I hope that this change brings noticeable differences faster JibberJobber, more reliable uptime, etc.  I appreciate your patience as weve worked our way through this, and look forward to having my developers spend more time on making JibberJobber better, and not as much time on reacting to bad guys. JibberJobber Speed Issues Update Thanks for your patience as we work through some speed issues weve had for far too long. This has been very frustrating for my team, not to mention expensive. Just today I was reading an article on my local news site about hackers.  Theres been plenty of talk about hackers, whether its because of the password leaks because of hacks into LinkedIn, Yahoo, and the hundreds of other high profile sites/cases, or because of the hacker influence on the 2016 U.S. presidential elections. Hackers seems to be a far away thing, not really impacting our day-to-day life (thats arguable, I know).  But it has definitely impacted me, my developers, and my users, every single day. Just yesterday we had a pretty light day only a few thousand hacking attempts were made. Only a few thousand. It made our server slower, because instead of just serving our users, it had to address the hackers requests.  So, users write us and report that it takes 20 or 30 seconds for a page to load. That is ridiculous, and unacceptable. My team gets distracted because I say stop what you are doing and lets address this.  That means that what they are working on gets put on hold and JibberJobber evolves and improves slower than it should. This problem is frustrating and expensive. It is also demoralizing to everyone involved. We have a plan moving forward, though.  Its like Plan B, but really, Plan L or J.  Weve been working on this problem for years. I think this is the right plan, though.  We have a new server admin involved, and will be switching JibberJobber to Amazons hosting environment. That makes me nervous just typing it, only because when we first launched JibberJobber Amazon was having all kinds of reliability issues it just didnt seem ready to host our stuff yet. But I think its time.  Were moving forward on switching to Amazon, the pioneer and leader in cloud hosting. Inherent in that move should be always-the-best hardware, as well as anti-bad-guy software to keep the hacking down.  Those are two great benefits of the move. In addition, the new server admin will be working on finding and identifying any place that he can help, including speed optimization, security, and other stuff (contingency, code delivery,  and other things the developers will know about, but users typically wont see). I hope that this change brings noticeable differences faster JibberJobber, more reliable uptime, etc.  I appreciate your patience as weve worked our way through this, and look forward to having my developers spend more time on making JibberJobber better, and not as much time on reacting to bad guys.