Специальный приз Linux Format

Проект Kalpa.Cloud (платформа разработки сетевых графических приложений) удостоился специального приза - "Выбор редакции Linux Format" в конкурсе "Лучший свободный проект России", проводимом журналом Linux Format при финансовой поддержке компаний Intel, PingWin Software, "ГНУ/Линуксцентр", WiMax Store при официальной поддержке Министерства связи и массовых коммуникаций Российской Федерации.

От себя и коллектива фирмы Olmax выражаю огромную признательность организаторам конкурса, членам жюри и лично Павлу Фролову, дружеские наставления и поддержка которого подвигли на участие в этом конкурсе.

Заключено соглашение о сотрудничестве с компанией - "Конструкторское бюро информационно-аналитических систем" (КБ ИАС).

Description of Technology.

Experience in developing network of information systems has enabled us to rethink the approaches to the creation of distributed network software and offer a solution to the problem - technology platform Kalpa.Cloud.

Decisions based on Kalpa.Cloud:

• Preventing leaks of corporate information
• Ease of administration.
• Savings of traffic.
  
• The ability of the customers to work at low speeds.
• Reducing the cost of maintenance of a Kalpa.Cloud-bases software system.
• Reducing the cost of hardware.
• Net applications with advanced graphical user interface.
• Same speed and comfort in a local network or on the Internet.
• Compact client realized for major operating systems.
  

We know and can articulate the requirements presented for modern, progressive companies.

Modern companies are actively expanding, creating remote branches.. In a geographically dispersed environment, requirements for integration into a single information system are not just a comfortable supplement, but the only possible condition for the survival of the company through the control and management of remote units.

Existing IT solutions developed in an era of local networks did not expect the work in a globalized world.

The main risks in modern information systems are corporate data leaks. Direct access to information allows staff to copy it to control external drives or transfer files over the network. Similar incidents have rightly called the main problem of modern information systems. Most embedded software architecture using a «thick client», which implies the existence on the side of the client uncontrollable array of data, or targeted to the «Documents». The first and second concept implies the possibility of unauthorized copying and data leakage. A particularly dangerous, such outdated architecture for use in mobile applications, or small remote offices, where staff with mobile computers can be directly compromised, or subjected to physical pressure in order to capture the computer and as a consequence, the information resource.

The concept of a centralized data repository on the server side and a thin client interface, allowing to solving these issues at the level of architecture. There are no user information, documents and materials stored at work. Access to information resources is possible only through a special interface. Malicious copied information is impossible. Portable personal computers did not become a zone of risk of information leakage. Remote small offices with under-developed security regime are protected from leakage and blocking the work through the information control or other harsh measures.

Effective maintenance costs during the economic crisis, suggests the possibility of rejection of their own expensive server resources and division of their support for the hosting of operators, thus locating the point of possible leakage of information. In this case, the determining factor of success becomes possible migration server infrastructure and speed the deployment of the complex.

System platform Kalpa.Cloud allow most effectively and quickly move the server part of the system to favorable or suitable sites within the corporate network, or rent the resources of external operators of auto sources.

For corporate users the claim advanced graphical user interface, which becomes decisive in addressing issues of ergonomics and efficient use of staff time. Obviously, the solutions-based HTML (web interface), using a standard Web browser can not meet these requirements. The volume of data generated and transmitted to ensure the interface requirements, the speed of generation of interface on the client side and cognitive ability web interface was not sufficient to ensure good corporate user needs.

System platform Kalpa.Cloud allows you to create network program indistinguishable from the local to the functionality, speed of response and cognitive properties.

Modern corporate information is multiplatform environment. A wide range of equipment and operating systems, increasing the share of Macintosh computers and Linux based systems, along with the traditional Windows systems, the use of lightweight (notebook) and pocket computer determines the requirement of multiplatform. Existing systems are typically mono-platforms and do not contribute to the development of heterogeneous networks.

System based on platform Kalpa.Cloud allows the client to use any of the most commercially successful operating systems.

We know that quality and provided flow does not always match the industrial demands of the corporate client. This is the same regarding the server connection and the client. The system of the server, serving a substantial number of client connections can consume a hefty network share. If we talk about a client, in a geographically distributed information environment, it may experience difficulties with the given bandwidth. Individual users may experience difficulties connected to mobile networks. The existing market information systems are usually very demanding for telecommunication resources. This applies as well to the server system and for the client connection. Increased demands are required for Web-based applications and terminal connections. It is known that the use of terminal solutions (Citrix) at the flow of 2Mb / s allows a server with good comfort for the user's service from 7 to 14 simultaneous connections, which is unacceptable for modern distributed information systems, the number of customers in more than 1000 compounds.

Platform Kalpa.Cloud originally designed as an extremely undemanding to telecommunications. Field tests showed the possibility to work with interfaces, even at speeds of 14400, and the user speed range (64K-256K) provide stable comfort.

The proposed technology in the market of network information systems is very resource-intensive. Web-based solutions platform Java (well as other well-known technology) does not allow coping with the load on the system that calls for the selection of the extensive development of computational tools. Troubleshooting usually lies in the acquisition and installation of expensive servers, industrial level or in the creation of cluster computing systems.

System platform Kalpa.Cloud kept the load on the corporate information environment, using standard computing systems in consumer or lower corporate level. In practice, this means that the Kalpa-effective solution would be to work on cheaper hardware.

The server is located in one place. Updating the software package comes on a single server machine, invisibly to the user.

Contacts

Oleg Shalnev

Network graphics applications.

Author: O. Shalnev

Rendered: D. Katsera

Reflecting on the situation in developing client-server systems that were forced to tasks, which require a different approach to that, which is now available on the market.

A history of network applications is well-known. From the early evolution of terminal stations led to a file-server solution, and then, with the advent of database servers, to the classic client-server systems, consisting of 2 parts, Server databases and "client". Such a scheme and now enjoys a well-deserved popularity and the nature of the popularity of technological simplicity of implementation architecture client-server. Access to database opened developer opportunities to manipulate the data masking mechanism for the exchange of information between the client and the server. The objective was the implementation of the programmer-friendly user interface and development of effective SQL queries. But on the other side of the weights are drawbacks 2 bridge model. First and foremost is the need to create a client program to be fully realized demo logic, and, sometimes, and the logic of the task itself. The full value of the client could be significant in case of heavy systems. This scheme became known as bunch of "thick client" to the database server.

Of course, if changes in the logic of the system or the interface of a need to update the client software on all workplaces users. This fact complicates the process of tracking systems, forcing developers to apply automatically maintain client program to date, the swap of modified modules. Supporters of 2-point approach from the world of Java, taking advantage of its platform to easily update the client program is putting himself in a credit score and typing in the discussions. Despite the advanced methods of software updates, is the need to update the client application remains.

The second problem is that the model is to publish a database server on the network. If a local decision, such an approach is let and acquitted in the case if the "problem" arises and begins to live in the boundless spaces of Internet-but publishing server bases in large networks has become a serious headache for system administrators. Embedded protection, authentication, encryption channels do not provide 100% secure.

Finally, the third complexity of 2-point architecture - is a possible demand of bandwidth channels. In a large, growing system is not always possible to monitor the effectiveness and wisdom of SQL queries. Often, requests and, more importantly, taken by motorcade server data is very large and can significantly reduce the speed of data exchange between server and client, to increase response time to requests that immediately affect the comfort of the user. This fact was well understood and helped the evolution towards of 3-chain architectures.

Under the phrase "three-tier" the people understand different. Many refer to three-tier architecture and terminal solutions. But whether such an understanding of things is justified? Can one attribute to the three-tier architecture terminal solution?

IT professionals have to use terminal solutions for the adaptation of two-tier systems in three-tier of contact with the "thin client". Terminal means are quite a lot. That decision, the use of X11 Protocol, Windows Terminal Service, Citrix, No Machine. But can these tools be used to be acceptable in the industrial exploitation? If you look, it shows that the very architecture of tasks, working in the terminal environment, usually written as a 2-makers and through the terminal means we actually camouflage bottlenecks two-tier model. Such decision is very demanding, both in terms of memory, and network resource. Indeed, starting application on the server side, you use memory not productively every time dragging a cargo of graphics and presentation logic. There is a certain need of a very solid server machine to ensure the normal operation of at least 30 client sessions. However, this depends on the resource problem. Reduced speed of the connection (client to the server) immediately affects the comfort of the user. Either the deteriorating quality of the image or raise boring delays is occurred. Advocates of terminal solutions are always talking about the relative modesty in consumption of telecommunications terminal client, neglecting to say about the server connection. Throughput of server connectivity – is a limited resource. It is not difficult to calculate how many simultaneous connections can accommodate a terminal server connected to the world at speeds of 2Mbit. Of course, terminal solutions are good, can and will occur as a tool for system administrator or privileged user, but if the server does not have to serve 30-40 and 300-400-5000 active compounds that can hardly be considered terminal scheme as a valid, reasonable, and the main thing possible.. And in vain adherents of "terminal schools" to think that small and medium businesses do not have tasks that do not fit a terminal service. For example in the information system of medium and small store can operate more than 40 jobs. Trading companies offer its partners access to information resources. Even small trading platforms may have a significant number of clients (traders). Thus it is understandable that for any large-scale solutions terminal means is not suitable. However, the terminal approach, paired with traditional two-tier model of development, remains the most popular and in demand. What is the reason for such popularity? Why are so expensive and resource demanding solutions to problems so attract developers. The reason for all is in the same ease of implementations. The programmers still do not have to think about "clients" and "servers", he only write a program using the library user interface and database access. Simplicity - the key to popularity. It is that simplicity luck in different approaches, as it will be described further.

Developers who want no surrogate, but the real three-tier model to understand the need to implement a balanced, devoid of graphics server load, and this "thin client" program that would only deal with interface. Developers were divided into several groups and each went their own ways. One group of armed conventional HTML browser and has used it as a "thin client". Parsimony of all available means to build the user interface is no confusion. However, very soon, hypertext mark-up language magazine pages became accrete additional "extras." However, no DHTML, nor layers and Java scripts has not radically changed the situation, but made it only more confusing. Browser war has made its share of problems adding for developers, forcing them to seek support of the maximum number of browsers. It is not added quality to the code but considerably increased the size of pages. But not even the size of pages and unfriendly interfaces become raise questions. The style and approach to the development of such systems differed from the comfort of the programmers of old classic two-tier systems. The need to think in terms of "pages" and "context client" had broken former server applications. The developer must generate by hands, either from a template the desired at the moment interface page. Enrich its content, while not forgetting to put it inside the control numbers. These targets will help the server remember what is at stake if the client suddenly wants to press button "A" in interface "B". And, of course, it must take the line from the client browser to deal with, and thereby control, status point is, in its memory of the image of the client session, to take certain actions and create a new page. It is rather difficult.

Of course, programmers have sought to simplify the development process making it similar to the classic. A variety of solutions began to appear. Many PHP libraries began to appear in different languages. Java world is particularly rich in such resources. But all this masking of architecture is the desire to make server software more straightforward and logical. In trying to make user interface more convenient, reasonable and modern began to appear special "thin clients" who worked with specially created for them page description language. Some languages integrated into browsers (XUL), but the principles of server software that does not change. Developers still lacks simplicity.

Another group of armed systems object brokering. RPC, CORBA, COM, DCOM, RMI, SOAP - the tools that allow developers to change attitudes to create applications. It is a tempting prospect to remotely create objects that cause the methods and procedures. True if a "client" will address himself to the server for remote procedures; it becomes a "thick" (rich client) client. If the "client" asks the server data for the current generation of interfaces, it is simply intellectual and complex browser. "Thin client" based on CORBA technology contains the entire set of interface tools, allowing "server" how to manage their resources. Some kind of remote, located on the client side repository of graphic tools. Wonderful idea, but it is difficult to implement. Programming Interface CORBA systems is not easy and not laconic. Certainly in the Java world, these issues are somewhat easier, but not all write in Java. And then, what is the creation of the interface? This is a long sequence of calling-type: create new window, paste button, type in button. Working with CORBA methods such sequences appear to be a big flow of small-sized packages to be prepared, shipped CORBA services and accepted by the other party. The sequence of small packages or variable causes slowing the processing of data in the TCP / IP stack. There is a view that the use of remote procedure call in case of need of extensive computation and not so often. This view is difficult to disagree with.

By analyzing the above approaches to address the development of client-server, author of the project Kalpa.Cloud set out to create a tool to meet the following requirements:

• Simplicity
  

• The programmer must create applications like ordinary graphics destop program.
• Programmer should not be difficult to encumber additional programming interfaces.
• The programmer should not be loaded with additional knowledge about how to organize interaction between the client and the server.
• The programmer should not think about the client side.
• The programmer should not think of the network side of a decision.
  

• Undemanding to telecommunications resources

• Interaction between the client and server must be at minimum speeds.
• "Thin client" as a means of customer interaction with the server.
• The client portion of the tandem should be minimal in size and undemanding to resources.
• The client portion should be cross platform and work for major commercial operating platforms.
• User "thin client" interacting with the server should not see the difference between normal local application and a network.

As a result of reflection and attempts to create the most convenient tool for the development of network applications, has been the emergence of the project "Kalpa.Cloud ". Kalpa.Cloud Instrument is a tandem library design for servers and" thin client ". Library provides developers to not think about all the complexities of creating network applications, but concentrate on creating the program. Programmer supplies with advanced set of tools that are familiar to the developer of the user interface. An opportunity to freely operate such concepts as "window", "frame", "menu", "button" and other well-known arsenal of tools for graphics libraries. Cross platform achieved by the well-known library Qt, Developer Company is called TrollTech. Naming classes, the parameters of functions and internal structures library Vedga is maximum identical to naming in Qt. Supported mechanism signals and slots that became the hallmark of Qt. In that developers Vedga see additional benefits to a large reservoir of programmers using Qt in their practice, easily adapted in Kalpa.Cloud. Moreover, it is possible to transform the existing Qt applications in the network. Easy and fast way to design allows fully move the load on the server side, providing "client-only interface functions. The interface wrapper library Kalpa.Cloud is hiding mechanism of transport management information and data between the client and the server. Optimization key algorithms have been assembling requests and answer packets in the packages and transfer data prepared in summary form. Achieved client-side comfort from the use of the network Kalpa.Cloud program is identical to the maximum comfort of working with the usual local program. You are the interface to which it is used in all its functional diversity and is not known discomfort of working with interfaces based on HTML browsers. The work of a programmer using the library Kalpa.Cloud becomes a server program (Daemon), is fully ready for operation.

In this example, you can see how close the methodology of establishing a network Vedga-annex to the methodology for creating applications in Qt.

KGroupBox * Window:: createSecondExclusiveGroup ()
{
 TransportPacket Packet;
 KGroupBox *groupBox = new KGroupBox(tr("E&xclusive Radio Buttons"), this);
 groupBox->setCheckable(true);
 groupBox->setChecked(false);

 KRadioButton *radio1 = new KRadioButton(tr("Rad&io button 1"), this);
 KRadioButton *radio2 = new KRadioButton(tr("Radi&o button 2"), this);
 KRadioButton *radio3 = new KRadioButton(tr("Radio &button 3"), this);
 radio1->setChecked(true);

 KCheckBox *checkBox = new KCheckBox(tr("Ind&ependent checkbox"), this);
 checkBox->setChecked(true);

 KVBoxLayout *vbox = new KVBoxLayout;
 vbox->addWidget(radio1);
 vbox->addWidget(radio2);
 vbox->addWidget(radio3);
 vbox->addWidget(checkBox);
 vbox->addStretch(1);
 groupBox->setLayout(vbox);

 return groupBox;
} 

As you can see the differences are insignificant. The result of the program, a fragment of which was presented earlier, on the client side looks the same as for X11 platforms, and for Ms Windows. These capabilities enable developers to base position Kalpa.Cloud as a tool for creating Internet applications with advanced user interface. A simple programming server (identical to the principles of conventional programming graphical applications) gives developers more options for creating a modern network applications and approaches to the creation of a unified corporate information environment.

Описание технологического предложения

Опыт разработки сетевых информационных систем позволил нам переосмыслить подходы к созданию распределенных сетевых программных комплексов и предложить свое решение проблемы — технологическая платформа KalpaCloud.

Решения на базе KalpaCloud это:

• Сетевые графические приложений с развитым пользовательским интерфейсом.
• Сетевой доступ удаленных филиалов и пользователей. Одинаковая скорость работы и комфорт как в локальной сети, так и в сети Internet.

• Недопущение утечек корпоративной информации

• Простота администрирования.

• Поддержка основных операционных систем.
  

• Экономия трафика. Возможность работы клиентов на низких скоростях.

• Снижение стоимости аппаратного обеспечения.

Мы знаем и можем сформулировать требования к современным системам, предъявляемые прогрессивными компаниями.

Компания OLMAX предлагает услуги разработки современных сетевых приложений с развитым графическим интерфейсом.

Снижение стоимости аппаратного обеспечения

Предлагаемые на рынке технологии организации сетевых информационных систем весьма ресурсоемки. Веб-решения на базе платформ Java (впрочем как и иные известные технологии) не позволяют справиться с повышенной нагрузкой на систему что вызывает необходимость в выборе экстенсивного пути развития вычислительных средств. Решение проблем обычно лежит в области приобретения и установки дорогостоящих серверов промышленного уровня или в создании кластерных вычислительных комплексов.

Комплекс должен обслуживать максимальное число пользователей даже на компьютерах потребительского ценового диапазона.

Решение

Системы на платформе KalpaCloud позволяют удерживать нагрузку на корпоративную информационную среду с использованием стандартных вычислительных систем потребительского или нижнего корпоративного уровня. На практике это означает, что Kalpa-решение будет эффективно работать на более дешевых компьютерах.

Описание технологического предложения.

Экономия трафика. Возможность работы клиентов на низких скоростях

Известно, что качество связи и предоставляемые потоки далеко не всегда соответствуют промышленным запросам корпоративного клиента. Это одинаково касается как серверного подключения, так и клиентского. Система, со стороны сервера, обслуживая существенное число клиентских соединений, может потреблять изрядный сетевой ресурс.

Если говорить о клиенте, то в географически распределенной информационной среде он может испытывать затруднения с предоставляемой полосой пропускания. Особые сложности могут испытывать пользователи, подключаемые по мобильным сетям. Существующие на рынке информационные системы, как правило, весьма требовательны к телекоммуникационному ресурсу. Это равно относится как к серверной части системы, так и к клиентскому подключению. Повышенные запросы требуются и Веб-приложениям, и терминальным подключениям.

Так известно, что использование терминальных решений (Citrix) на потоке 2Мб/с позволяет серверу с удовлетворительным комфортом для пользователя обслужить от 7 до 14 одновременных соединений, что совершенно недопустимо для современных распределенных информационных систем количество клиентов в которых может превышать 1000 соединений.

Клиент должен работать с максимальным комфортом на низких скоростях.

Сервер должен обслужить максимальное число клиентов на стандартных промышленных потоках.

Решение

Платформа KalpaFaces изначально проектировалась как чрезвычайно нетребовательная к телекоммуникационному ресурсу. Полевые испытания показали возможность работать с интерфейсами даже на скоростях 14400, а пользовательские диапазоны скоростей (64К-128К) обеспечивают стабильный комфорт.

На стороне сервера промышленно предоставляемые потоки позволяют не задумываться о сложностях при обслуживании большого числа клиентских соединений.

Описание технолонического предложения.

Поддержка основных операционных систем

Современная корпоративная информационная среда мультиплатформенная. Широкий спектр используемого оборудования и операционных систем, увеличение доли систем, использущих Linux и MacOs X, наряду с традиционными Windows системами, использование облегченных (netbook) и наладонных компьютеров определяет требование кроссплатформенности. Существующие комплексы, как правило моноплатформенны и не способствуют развитию гетерогенной сети.

Клиентская часть должна работать на основных операционных системах.

Решение

Системы на платформе KalpaCloud позволяют клиенту пользоваться любой из большинства коммерчески успешных операционных систем.

Описание технологического предложения.

Сетевой доступ удаленных филиалов и пользователей

Современные компании активно расширяясь создают удаленные филиалы. В географически разрозненной среде требования к интеграции в единую информационную систему становятся не просто комфортным дополнением, но единственно возможным условием выживания фирмы через контроль и управление удаленными подразделениями.

Существующие информационные решения созданы в эпоху локальных сетей изначально не предполагали работу в глобальном мире.

Решение должно быть доступно через локальную сеть или сеть Internet. Программа должна работать одинаково и в локальной и в глобальной сетях.

Решение

Системы на базе технологии KalpaCloud отвечают этим требованиям, что позволяет сразу ориентироваться на развитие, активно расширяясь не теряя эффективности в управлении удаленными подразделениями.

Описание технологического предложения.

Простота администрирования

Эффективизация расходов на обслуживание в условиях экономического кризиса предполагает возможность отказа от собственных дорогостоящих серверных ресурсов и отделов их поддержки в пользу хостинг-операторов, тем самым локализуя возможные точки утечки информации. В этом случае определяющим фактором успеха становится возможность миграции серверной инфраструктуры и скорость развертывания комплекса, простота управления информационной системой, легкость обслуживания.

Серверная часть системы должна легко обслуживаться, располагаться в одном месте.
Новые версии программы необходимо вводить в эксплуатацию максимально быстро и прозрачно для пользователей системы

Решение

Системы на платформе KalpaCloud позволяют

• максимально эффективно и максимально быстро переместить серверную часть системы на выгодные или удобные площадки внутри корпоративной информационной сети или арендовать ресурсы внешних операторов- аутсорсеров.
• Обновлять программный комплекс на одном компьютере незаметно для пользователей.
• Экономить на обслуживании.

Описание технологического предложения.

Недопущение утечек корпоративной информации

Главной опасностью современных информационных систем становятся корпоративные утечки данных. Прямой доступ сотрудников к информации позволяет бесконтрольно копировать ее на внешние носители или передавать файлы по сети. Подобные инциденты справедливо называются основной проблемой современных информационных систем. Большинство внедренных программных комплексов либо используют архитектуру «толстого клиента», что предполагает наличие на стороне у клиента неконтролируемого массива данных, либо ориентируются на «документы». И первый и второй концепт подразумевает возможность несанкционированного копирования данных и их утечку. Особенно опасна подобная устаревшая архитектура при использовании в мобильных приложениях или малых удаленных офисах, где сотрудник с мобильным компьютером может быть прямо скомпрометирован или подвергнуться физическому воздействию с целью завладения компьютером и, как следствие, информационным ресурсом.

Система должна быть защищена от возможных утечек данных и несанкционированного доступа.

Решение

Концепция централизованного хранилища данных на стороне сервера и тонкий интерфейсный клиент, позволяет решить эти вопросы на уровне архитектуры. На рабочем месте пользователя никакая информация, документы и материалы не сохраняются. Доступ к информационному ресурсу возможен только через специальный интерфейс. Злоумышленное копирование информации невозможно.

Носимые персональные компьютеры не становятся зоной риска утечки информации. Удаленные малые офисы с недостаточно развитым режимом безопасности защищены от утечек и блокирования работы через информационное рейдерство или иные жесткие меры воздействия.

Описание технологического преложения.

Сетевые графические приложений с развитым пользовательским интерфейсом

Корпоративным пользователем предъявляется требование развитого графического интерфейса, который становится определяющим в решении вопросов эргономики и эффективного использования рабочего времени. Очевидно, что решения на базе технологии HTML (веб-интерфейс) с использованием стандартного Веб-браузера не могут соответствовать этим требованиям.

Объем генерируемых и передаваемых данных для обеспечения интерфейсных нужд, скорость генерации интерфейса на стороне клиента и когнитивные возможности веб-интерфейсов совершенно недостаточны для обеспечения нужд эффективного корпоративного пользователя.

Пользовательский интерфейс сетевой программы должен быть аналогичен традиционному и предоставлять все удобства обычной локальной программы.

Решение

Системы на платформе KalpaCloud позволяет создавать сетевые программы неотличимые от локальных по своей функциональности, скорости реакции и когнитивным свойствам.

Описание технологического предложения.

Загрузить (Download)

Kalpa.Cloud Source Code (master branch)

Контакты

Олег Владимирович Шальнев. (Руководитель проекта.)

email: oleg@kalpa.ru
phone: +7(918) 741-72-17