#eWEEKchat Tentative Schedule for 2020 January: Trends in New-Gen Data Security February: Batch Goes Out the Window: The Dawn of Data Orchestration March: New Trends and Products in New-Gen Health Care IT
This has been a wonderful discussion. Outstanding interaction and engagement. about 200 posts, 1.9 Twitter impressions, all in 52 minutes! (data up in RH corner of the CrowdChat page!)
I do see an even shorter lifetime for software (infrastructure and otherwise) moving forwards. The rate of change is impressive and scary at the same time.
1. Serverless will NOT take off as people expect. 2. We will see more #Kubernetes failure stores but this will be VERY healthy for increased adoption 3. A lot more stateful/data-drive cloud-native application growth 4. A lot more use of multiple clouds together
Too much of global infrastructure,relies on aging technology vulnerable to exploitation. RSA expects to see nations bolster industrial control system (ICS) monitoring and defenses, in hopes of fending off increasingly commonplace and devastating attacks!
1. TypeScript will eat up even more of JavaScript's market share in 2020. 2. Programmable banking for individuals 3. More sophisticated IoT actuators for home automation. In general a huge takeoff in IoT in the home. No-code programming tools for IoT at home.
to paraphrase Bruce Lee --- "the art of IT without IT" ... people in LOB will make great strides in building, deploying and managing their own applications
@RingCentral Couldn't agree more - we're seeing many organizations rationalize the apps they use, there is far too much cost, and potential risk to let this continue unchecked.
With global events (i.e. Summer Olympics) delivering experiences through a blend of infrastructure and connected systems, cybersecurity will move beyond data to encompass more and more of our physical well-being or “cyber safety.”
Data governance will become an increasingly talked about problem amongst IT leaders. The "democratization" of IT is causing incredible data governance and security problems.
@HowardMCohen yes actually. Among the best organizations adopting citizen dev platforms, we're seeing a lot of investment in governance. It's actually a lot easier with no-code platforms than it is with traditional code apps.
Customer stories around complexity, code maintenance pain two weeks in, hype around it being the next big thing (vs. an important part of a dev's toolbelt), lack of a standard, insufficiently large ecosystem.
@ASGTec 2. Shift away from monolithic, purpose-built #applications to new, nimble applications that serve a specific function and can be built on top of existing #services. #eWEEKchat
@simoncrosby The question is who provides the bridge for folks with "legacy" skills. I think VMware is actually making moves in the right direction there.
@gssor Democratization of IT is a trend that isn't going away and is benefiting business productivity. So rather than "problems", I think of it as bringing needs.
@simoncrosby Would love to see #serverless become #stateful. EKS of Fargate was really interesting but no stateful just yet. That said, I can see a success path down that route.
Accountability for cyber risk will move up the org chart, with forward thinking businesses appointing board members with experience in risk management and information security.
worry, yes, but the tide appears to have turned on this. When even Gartner promotes it at keynotes, it's looking like citizen dev is becoming mainstream and IT has to figure out how to enable it in a sensible way
@gssor not really. I've spent some time learning about it. It is basically a way to spin up "APIs" on legacy systems that only have UI. It used to be that humans provided that interface, now RPA systems do.
@nirajtolia to me, RPA feels like a stop-gap solution to squeeze further life out of antiquated systems. So it isn't strategic, it feels completely tactical. Valuable no doubt.
@gssor Agree from a technology point of view, but I see a lot of tech people (myself included initially) diss RPA for this reason. Until I realized it was solving a real customer problem that there isn't another immediate solution for.
