EVA ICS v4 architecture (draft)

EVA ICS v4 is going to be released this year. How is it different from EVA ICS v3?

Take a look on the schema. The first one is v3 architecture we’ve been using since 2017. And here are the key problems with it:

  • The monolith core, written in Python
  • After 4 years, the core has got about 6 types of extensions (drivers, core scripts, plugins etc.)
  • Majority of plugins can be written in Python only and work directly inside the core, which reduces its stability and performance
  • Limited CPU scalability
  • Each enterprise setup is unique and requires unique features. All of them go to the core, slowing it down and making it more and more complicated.

But things will be completely different in v4.

Continue reading “EVA ICS v4 architecture (draft)”

Future of EVA ICS

EVA ICS version 3 has become the most successful industrial IoT product of our company. It already has dozens of setups we support directly and I hope even more setups we don’t.

But the version 3 has a problem: because of the rapid numbers of customers and features growth, it’s internal architecture was changed several times almost from scratch, lots of stuff already became obsolete and too complicated for beginners.

Here are the plans for the EVA ICS codename “nextgen” (next generation):

Continue reading “Future of EVA ICS”