Switzerland suspends this league day because of the coronavirus

first_imgAlso, seeing the calendar so tight and to follow the League normally, the institution values ​​playing games behind closed doors but they still have to decide with the clubs, who have not expressed their position regarding this solution.The matches suspended in the First Division are Sion-St-Gallen, Young Boys-Zurich, Lucerne-Basel, Servette-Lugano and Xamax-Thun. In Second the Laussane Ouchy-Chiasso, Kriens-Schaffhausen, Wil-Lausanne and Vaduz-Wintherthur will not be played.In addition to the League, Switzerland has also been forced to suspend the Geneva Motor Show, one of the most important events of the year in the motor world. The Swiss League will have to stop for the measures taken by the Swiss government to prevent the spread of the coronavirus, which in the country already accumulates up to 15 positives by Covid-19. The executive has banned any type of event that exceeds one thousand people capacity until March 15 and the Swiss League (SLF) has folded to government requirements postponing this day 24 in First and Second Division.In an official statement, the League informs of this suspension and leaves the new date for this twenty-fourth day, which they indicate, will be decided next week.last_img read more

Microservices and containers are perhaps the great

first_imgMicroservices and containers are perhaps the greatest potential change in how IT organizations deliver and run software services since the arrival of virtual machines. Such a change brings with it lots of interest and enthusiasm, and inevitably much hype and bandwagon-jumping, too.But, amid all the noise, let’s not forget that it’s early days yet—not just for the technologies, but especially for the processes and practices around microservices and containers. Pretty much everything in this space is either still waiting to be invented or needs a lot of fine-tuning.Given the incredibly rapid pace of change in this area, it’s essential you have a clear understanding of the capabilities of the technologies and experience level of your teams before making any implementation decisions. Bottom line: Doing research is absolutely not the same thing as going for full-scale adoption. Production is never a good arena for R&D.Here are six important questions organizations should ask before moving beyond research: 1. What is your business need? Perhaps the most fundamental question you and your company need to answer before deciding to adopt microservices or containers is whether there is a real business problem that needs to be solved—one that cannot be solved satisfactorily with your existing approaches or technologies. Microservices and containers are new, evolving fast, and still not very well understood, all of which represent risks that need to be balanced by some concrete benefits for your teams and organization. 2. Do you have the engineering know-how? If you are convinced that microservices and/or containers do indeed promise to solve a problem that you can’t address in other ways, make sure you have access to expert platform engineering resources, because you will need them. This issue extends well beyond the fact that APIs and frameworks are pretty much brand new. Getting a container-based platform up and running in production means solving many “adjacent” problems that the current frameworks cannot address, such as optimizing networks, deciding on storage strategies, handling backups and failover, dealing with security, and so on. 3. Are you willing to learn as you go? At present, there are many more questions around production-ready microservices and containers than there are answers. Even if you have the right engineering expertise to handle the challenges, you should be prepared for a multi-year period of ongoing experimentation and learning.At least some of the APIs and frameworks you will choose will undergo significant, backwards-incompatible changes or even fall by the wayside entirely. You will also need to rip and replace others that turn out not to be suitable or mature enough for your scenario. Finally, there’s the matter of best practices for everything from operational procedures to app delivery patterns; be prepared to develop these yourself.last_img read more