14 – 18 June warned Windows 2000 users of looming support freezes, gawked in awe at JIT, shared Julian’s LinuxTag presentation, introduced the SOAP and REST developer conflict and announced our first Icinga addon.
Reflecting on hot summer days in data centers, Jannis revealed Heatmap for Icinga. Now while enjoying ice cream, admins can view their server room and react quickly to temperature problems. With a drag and drop, servers and sensors can be laid out on the map and intervals for temperature processing set. Replete with dashboard, it integrates seamlessly into Icinga Web and is ready for download at netways.org as always.
We paid our respects to JIT (JavaScript InfoVis Toolkit) while Julian shared his presentation slides from LinuxTag in Berlin on Nagios and Icinga. He then went on to bring bad news to Windows 2000 users – as of 13 July 2010, Microsoft will end support for all Windows 2000 regardless of type. This means no free updates or security updates, which may also mean security problems will no longer be fixed. On the same day, normal support for Windows 2003 Server (and Server R2) will run out and only extended support will be provided. So only issues critical to security will be fixed, for all others a patch will be offered only to those in their paid support program. This extended support will be available to 14 July 2015- so it seems now is high time to switch out!
Finally, Bernd introduced his new series to tackle the SOAP or REST question which all developers inevitably face in service oriented development. He plans to look at both architectures in detail and compare their advantages and disadvantages. In the meantime he pointed to a previous post from Julian for a good starting point. Till then, keep your eyes peeled!
NETWAYS Blog
SOAP oder REST: Was ist los?
Im Bereich der serviceorientierten Entwicklung steht der Developer häufig zu Beginn vor der entscheidenden Frage:
SOAP oder REST
Gleich vorweggenommen sei die Tatsache, dass auch diese kleine Serie keine universelle Antwort auf eine solche Frage geben kann. Es ist vielmehr der Versuch etwas Licht ins Dunkle zu bringen und die Vorteile beider Möglichkeiten zu erörtern. Letztendlich geht es wie immer um die richtig Lösung für die vorhandene Aufgabenstellung und vorhandenem Knowhow.
Grundsätzlich trifft es das Bild von Julian’s Blog Post ganz gut, jedoch ist die Tatsache das wenig „gesprochen“ wird nicht nur ein Vorteil.
Die nächsten Tage werde ich auf beide Architekturmodelle etwas detaillierter eingehen und deren Vor- und Nachteile erörtern.
(via Geek And Poke)
Soap Is Much More Polite Than Rest
Aus dem fantastischen Blog Geek And Poke