![\"\"](\"https:\/\/global.bg\/en\/wp-content\/uploads\/2019\/02\/2.png\")
<\/figure><\/div>\n\n\n\nA bundle that has\nserved well not only to Global Consulting and our customers, but also many more\npeople and companies around the world, despite the insignificant changes it has\nundergone in the past 5 years.<\/p>\n\n\n\n
The goals we have set<\/h2>\n\n\n\n
Our goal was to have a set of software\ntools and technologies to create web-based applications to\n“multitask” on several levels:<\/p>\n\n\n\n
To meet the increased customer requirements<\/h3>\n\n\n\n
For better or worse, clients are getting more and more demanding. And we adapt by making the user\nexperience richer and screen scenarios implemented with HTML5 and JavaScript\nmore complex. Tools and technologies should look good on screens with different\nresolutions. Be more secure than ever. They should, unlike people, work 24\/7 and respond\nefficiently to peaks in user activity activity.<\/p>\n\n\n\n
Be able to deploy in virtual and cloud infrastructure<\/h3>\n\n\n\n
We expect web applications to work both in our\ncustomers’ IT infrastructure and in cloud environments. No, we do not mean an\nenvironment where there is no sun and black clouds foreshadow a hail, but a\nprivate cloud built with virtualization tools or public cloud service. The\ntechnologies used to build our web applications need to be optimized for\nhigh-performance work in an environment with limited and competitive resources.<\/p>\n\n\n\n
Our requirements do not end here. We also want from web based applications:<\/p>\n\n\n\n
The platform should not be explicitly dependent on Windows<\/h3>\n\n\n\n
Microsoft Windows\nis great, but it is important for us that Global Web Applications can also work\non Linux-based servers to take advantage of advanced deployment schemes for our\napplications, such as Docker Containers.<\/p>\n\n\n\n
Make the most of our team’s existing know-how <\/h3>\n\n\n\n
Not to brag\nexcessively, but our team has more than 20 years of experience in engineering information systems, putting\nthem into operation, maintaining them and further developing them.<\/p>\n\n\n\n
Taking this into\nconsideration, it would have been a rave\ndecision to ignore\nthis experience and start learning from scratch. The new technology tools we\nwere going to use had to make the most of our experience and allow a relatively\nsmooth continuation of maintenance and development of existing Global\nConsulting systems.<\/p>\n\n\n\n
The solution<\/h2>\n\n\n\n
In our decision there was an easy part about which we had few worries, and one that was accompanied by doubts, some head scratching, and curiosity about what would “pop out of the hat.” The new web applications in Global Consulting (and newer versions of existing applications) to date are implemented using the following software tools: <\/p>\n\n\n\n
![\"\"](\"https:\/\/global.bg\/en\/wp-content\/uploads\/2019\/02\/3.png\")
<\/figure><\/div>\n\n\n\nThe easy part\u2026<\/h2>\n\n\n\n
…was\nthe switch to ASP.NET Core.<\/p>\n\n\n\n
Our experience for the past year and a half\nhas shown that the transition is practically unimpeded. The process of work\nwent smoothly, and we did not find hidden traps along the way. Considering the experience\nwe have gained so far with .NET, we needed just a little bit of\n“upgrading” so we could make full use of the .NET Core features and\nbenefits. From a purely programmer point of view, there is no difference<\/strong> whether the C # code is referencing to .NET Core or the full .NET\nFramework.<\/p>\n\n\n\n There are some software design templates, where the utilization is even easier to achieve with ASP.NET Core compared to traditional\nASP.NET – such as the use of Onion Multilayer Architecture, Dependency\nInjection, and more. This is because these design templates are embedded at the\narchitectural level in the new .NET version.<\/p>\n\n\n\n ASP.NET Core architecture allows the app to be\ntargeted for compiling and running both to the .NET Core and the full .NET\nFramework.<\/p>\n\n\n\n In case you’ve already lost the thread, let’s note what we have covered\nin a summary:<\/p>\n\n\n\n … came from abandoning the traditional web applications <\/strong>where almost all presentation logic (user interface) that is generated by HTML and JavaScript is executed on the web server along with the business logic. Virtually any significant user action generates a full query to the web server where it is handled and returns an HTML result to the client, which more often causes a full load of the entire web page in the browser. Yes, there may be separate user interface snippets that enrich the user experience and work entirely in the browser with jQuery and AJAX queries. But they are few or very isolated, their use is fragmented, and at a time when these fragments become too many, the efforts to maintain and develop them become unreasonably large. <\/p>\n\n\n\n From these traditional web applications we\nswitched to…<\/p>\n\n\n\n …<\/strong>Single\nPage Applications (<\/strong>SPAs)<\/strong>, where presentation logic is fully executed in the browser, and the\nbusiness logic is running on the web server. This is a one-step advance in the\nweb application implementation of one of the basic principles of software\nengineering – Separation of Concerns.<\/p>\n\n\n\n Typically, in SPA applications, there is a\nstatic home page (index.html), from which all the JavaScript and CSS resources\nrequired for the entire web application are loaded in the client browser. In\nthe process, the communication between the browser’s SPA application and the\nweb server’s business logic is performed through JSON Web API queries.<\/p>\n\n\n\n In these web applications, a rich user experience is set by default. It is integrated into the framework used to develop the application – all user elements on the page (HTML tags and CSS) are created and managed dynamically by JavaScript by manipulating the DOM in the browser. It is good to note that the efforts for maintenance and development of the rich user interface are fewer than the traditional approach. <\/p>\n\n\n\n To date, when talking about developing SPA web applications, React, Angular, and VueJS are most commonly referred to. This topic can become a scandal with apocalyptic proportions among the more passionate supporters of one or the other technology. We would even say that Angular VS React VS Vue JS is something like the modern IT version of the feud between Montecchi against Capulet … Or Arsenal against Tottenham if you like that better. You can come across some interesting memes and pictures on the topic online \ud83d\ude0a <\/p>\n\n\n\n We will not participate in this dispute, at\nleast not in this blog post.<\/p>\n\n\n\n Here we will only share our reasoning behind choosing Angular<\/strong>.<\/p>\n\n\n\n It includes everything (or almost everything)\nthat you need to develop complete SPA web applications – MVC engine, HTTP\nClient, Routing, strict and clearly defined system for the use of modules, own\nUI library – Angular Material, Angular Flex Layout, own set of client tools for\nuse by developers, etc.<\/p>\n\n\n\n Yes, compared to other technologies, it may be\na bit “heavier”, but our goal is not to carry a backpack in the\nmountains, but to develop, enhance and support\ncorporate web applications (relatively large and inherently “heavy” web apps). In\nthis sense, this is the right tool for us.<\/p>\n\n\n\n Angular shares many of\nthe software design templates known to developers with ASP.NET MVC \/ ASP.NET\nCore background and other object-oriented frameworks. For example:<\/p>\n\n\n\n The already mentioned Model-View-Controller.\nFor each Angular component, we have a split between an HTML template and component\nprogram code written in TypeScript and separate classes with Data models also\ndescribed with TypeScript.<\/p>\n\n\n\n TypeScript is a very adequate way to put order familiar from object-oriented languages into JavaScript! While it is possible that things do not look that way for people who do not have backgrounds in C # or Java <\/em>\ud83d\ude0a.<\/em><\/p>\n\n\n\n In Angular, the use of software services,\ndependency injection, modules is primarily covered.<\/p>\n\n\n\n Angular uses the fresh RxJS library to\nachieve a high level of reactivity in the interaction between the components\nand the dynamic exchange of information between them.<\/p>\n\n\n\n Behind Angular, behind the entire framework,\nwith all its core components, is one of today’s giants in the software\nindustry, Google, with a clear position to maintain and develop the technology.\nThis is an important factor when selecting a tool for the implementation of a\ncorporate software system, which in turn should also be supported and developed over a relatively long period of time.<\/p>\n\n\n\n Other than that another modern software giant,\nMicrosoft, has shown a clear commitment to support the Angular Framework in its\nown technologies. Both in TypeScript and in the ability to integrate Angular\nSPA into the ASP.NET Core Technology Stack.<\/p>\n\n\n\n In other words, with Angular we are set on two fronts, both of which are reliable\nenough.<\/p>\n\n\n\n Dogmatic, because you can not do whatever you\nwant. When it comes to the Angular Framework, “there’s only one version of the\ntruth, and it is has been\ncreated by Google” That is, there is a clear set of\nrules and good practices that are defined by the developer of the framework,\nand when programmers develop\nusing Angular they have to\nfollow them. Full stop. The end. Point finale.<\/p>\n\n\n\n If you do not like this approach or you do not like the specific rules\nand practices define<\/em>d by Google,\nAngular is probably not your SPA framework<\/em> of preference and you have to <\/em>look for\nsomething else to design your saunas (again “ha<\/em>-ha” ).<\/em><\/p>\n\n\n\n The documentation of\nthe entire framework is very good, extensive, supported in one place and\nupdated in a timely manner<\/strong> with\nchanges to the versions of the framework itself.<\/p>\n\n\n\n All important factors when you have a team of\ndevelopers who have to work on the support and development of several corporate\ninformation systems and who are required to follow a unified set of practices in\nsoftware development and maintenance.<\/p>\n\n\n\n In retrospect, the only major challenge Global\nConsulting encountered in our transition to the use of Angular was the initial\nfamiliarization of the team with the framework.\n\nEach of\nus, who had not encountered SPA\nlibraries in practice so far, had to take the time to complete Angular\ntraining. Fortunately, there are enough resources on the internet in the form\nof courses, and as mentioned above, the Angular documentation is quite complete\nand good. And as we are capable, clever and modest professionals, things have\nhappened smoothly and without any particular catastrophic\nconsequences.\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":" The Question The “hectic everyday life” clich\u00e9 haunts us everywhere: television gurus recommend observing the sky daily to prevent depression and bad fortune, and celebrities prescribe hackneyed and eccentric recipes for stress relief and endless spiritual relaxation. We do not know whether the “hectic everyday life” is such a dramatic problem, but one thing is certain: in the world […]<\/p>\n","protected":false},"author":8,"featured_media":1009,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false},"categories":[41],"tags":[66,60,64,65,34],"yoast_head":"\nThe interesting part\u2026<\/h2>\n\n\n\n
![\"\"](\"https:\/\/global.bg\/en\/wp-content\/uploads\/2019\/02\/4.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/global.bg\/en\/wp-content\/uploads\/2019\/02\/5.png\")
<\/figure><\/div>\n\n\n\nAngular? What is that?<\/h2>\n\n\n\n
![\"\"](\"https:\/\/global.bg\/en\/wp-content\/uploads\/2019\/02\/6.png\")
<\/figure><\/div>\n\n\n\nAngular is a complete SPA development framework<\/h4>\n\n\n\n
Angular and famous software design templates<\/h4>\n\n\n\n
TypeScript<\/em><\/h4>\n\n\n\n
Angular – Google technology and not just that …<\/h4>\n\n\n\n
Angular is a dogmatic (opinionated) framework<\/h4>\n\n\n\n
Challenges<\/h2>\n\n\n\n