Blog

Scrum Guide – what has changed? 2020 November update With all the events that happened in 2020 worldwide it’s not difficult to miss the latest update to the guidelines of the most popular agile framework – the Scrum Guide. In this article I outline the most important changes and assess their impact on teams’ everyday […]

Scalability in web applications has become crucial in the past years. An ever-growing number of devices and clients, connected to the Internet, makes it difficult to handle the traffic by a single server. Scalability is a characteristic of a system that tells if expanding the resources of a server(s) will make it run faster (or handle more load).

DevOps is an innovative methodology that introduced a new quality of work on IT projects. It is based on the cooperation of autonomous areas: software engineering, system administration, and issues related to safety and quality. The result is a combination of developer competence (Dev), system management (Ops), and most importantly,  operating culture. The DevOps concept assumes close cooperation between the programming team and the operational team.

Process of the product development consists of many steps that are often very complicated, time consuming and not well defined. It is common that companies are struggling to track the progress of the development and keep the documentation up to date. The main challenge that I would like to focus on is the continuous need to improve the product. Because we do not live in the perfect world the changes are unavoidable – whether it is just small fragment of the design that needs to be updated, the part you have been using so far is no longer available or you have to make sure that the product meets the requirements of the new markets.

Modern web applications that serve data and content to millions of users run in clustered environments. Dealing with a huge amount of connections at the same time requires many resources. That resources are CPU time and RAM. Each and every connection produces an additional load on the server. Having just one server would require a vast amount of resources and we already know that Moore’s Law is no longer valid. That said we need multiple servers ready to respond to users’ requests. Web applications use HTTP(S) protocol which works in the request-response communication method. Upon user’s request, the server will prepare the response and send it back. Every response needs to be processed by the server and that’s the key factor in provisioning resources for the server – requests may be different, starting from simple static data like CSS or images to more demanding like requesting data from database, filtering or calculating certain data.

Windchill is PTC’s flagship Product Lifecycle Management software, which has its latest version this year – WNC12. The long-announced premiere, scheduled for 2020, was questioned due to the COVID-19 pandemic. But PTC did not disappoint – on 9th June, at the fair in Boston, it announced the release of the latest version of its product lifecycle management (PLM) software. Windchill, which is considered a model example of an Enterprise Class System, has gained new functionalities. What is the potential of the latest, twelfth version of this program? We decided to analyze it for you.

The ThingWorx IoT Hub Connector is the bridge that connects the ThingWorx platform to the Azure cloud (more specifically to Azure IoT Hub). It provides secure (certificate-based) communication, thanks to which we can use the enormous possibilities of cloud computing. It is also a very extensive, but generic solution.

The year 2020, and especially its end, is the time of changes announced by the producer of Jira software. Recently, we have heard about the new licensing and support conditions for Atlassian Server products, and today (November 9, 2020), the company announced the rebranding of their Jira Service Desk. Apart from the new name – Jira Service Management, customers will receive a complex, comprehensive ticket management system. So far, Jira Service Desk has been enriched with many useful functionalities through add-ons. Now it will have them by default, which is a huge step towards meeting the needs of business customers.

With Cloud technologies developing rapidly in recent years, so came the thought of using the Cloud for hosting various systems in it, from computationally demanding, through mission critical and more. Product Lifecycle Management (PLM) systems were no different and a large number of both PLM vendors and customers attempted to leverage benefits the Cloud brings to gain that competitive edge world’s best manufacturers always strive for.

Synergy, this is how you can define this natural combination of technologies that will significantly affect the appearance of the future of production. Recently, in addition to the Internet of Things (IoT), artificial intelligence (AI) is gaining more and more popularity. The connection of these two technological trends heralds a real revolution in industry 4.0.

What does Jira Cloud have that Jira Server doesn’t? What benefits does it offer, what functionalities are worth noting, and do both these hosting options imply the same way of accounting for maintenance? Here we present the most important differences between Jira Cloud and Jira Server. You should get to know them before making a decision on implementing or migrating your company’s software.

Product Lifecycle Management (PLM) vendors promise their systems to be so great, they can be used by organizations from the get-go, revolutionizing how they define and manage their product data. However, that is the case only for those organizations who are willing to adapt their own internal standards and procedures for the sake of pre-implemented best practices within PLM systems.