# Web Services Published articles for Web Services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chainguard Image now available for Zig DevFeed: [Chainguard Image now available for Zig]() Original publisher: [Read original article]() Published: 2023-08-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Zig](), [chainguard](), [Docker](), [Dockerfile](), [WebAssembly](), [CI/CD](), [Containers](), [Application Development](), [Programming](), [systems]() Tags: [application-development](), [build](), [c-plus-plus](), [chainguard](), [chainguard-images](), [ci-cd](), [code](), [containers](), [cve](), [deployment](), [docker](), [docker-image](), [memory-safety](), [security](), [toolchain](), [vulnerability-management](), [wasm](), [web](), [web-services](), [webassembly](), [wolfi](), [zig]() ### AI overview Chainguard introduces a Zig container image built from its existing Wolfi Zig package. The article explains how to use the image for development, CI/CD, production Docker builds, and server-side WebAssembly workloads, highlighting its 96MB size and zero known CVEs. ### Source excerpt Introducing Chainguard Image for Zig: Bridging superior security and seamless Zig application deployment. ## API Development Tips DevFeed: [API Development Tips]() Original publisher: [Read original article]() Author: Federico Published: 2018-06-18T12:45:00Z Content type: tutorial Language: en Sources: [Federico Cargnelutti]() Topics: [API](), [Development](), [backend-development](), [Server]() Tags: [api](), [development](), [errors](), [external](), [latency](), [monitoring](), [node-js](), [pitfalls](), [releases](), [router](), [servers](), [software-architecture](), [standards](), [test](), [tips](), [web-services]() ### AI overview This article presents five practical tips for developing reliable open web APIs: test beyond unit tests, plan for future versions, embrace standards, monitor honestly, and design failures well. ### Source excerpt Organisations who are paying attention already know they need to have an open web API, and many already have under development or in the wild. Make sure you haven't been caught by the pitfalls of many early API releases. Multiple points of failure: The 5 tips Test it all Plan for future versions Embrace standards [...] ## Website performance monitoring tool DevFeed: [Website performance monitoring tool]() Original publisher: [Read original article]() Author: Federico Published: 2016-08-01T16:54:00Z Content type: article Language: en Sources: [Federico Cargnelutti]() Topics: [Monitoring](), [Website](), [dashboards](), [Open Source](), [Self-hosted](), [GitHub]() Tags: [dashboards](), [github](), [javascript](), [monitoring](), [node-js](), [open-source](), [performance-metrics](), [performance-monitoring](), [self-hosted](), [slack](), [tool](), [tools](), [web](), [web-apps](), [web-services]() ### AI overview The article introduces SpeedTracker, an open-source, MIT-licensed, self-hosted tool that runs on WebPageTest to periodically test website performance. It visualizes performance metrics over time, supports performance budgets, and can send alerts by email or Slack. ### Source excerpt Monitoring systems allow you to monitor changes to your front-end code base over time, catching any regression issues and monitoring the ongoing effects of any performance optimisation changes. Easy to use dashboards are a must when it comes to monitoring the state of your web apps. Companies like Calibre or SpeedCurve offer this as a [...] ## Interfacing Frege and Ring DevFeed: [Interfacing Frege and Ring]() Original publisher: [Read original article]() Published: 2014-12-21T00:00:00Z Content type: tutorial Language: en Sources: [Adam Bard]() Topics: [ClojureScript](), [Haskell](), [Java]() Tags: [clojure](), [functional](), [haskell](), [interop](), [java](), [type-system](), [web-services]() ### AI overview This tutorial explains how to interface Frege, a strongly typed functional language for the JVM, with Clojure and Ring. It describes using Frege for type-safe intermediary code, converting Ring request and response maps at the boundaries, and interoperating with Clojure maps through Frege's Java FFI. ### Source excerpt Frege is a strongly-typed functional language for the JVM. Its goal is to mirror Haskell as closely as is possible on the platform, and as far as I can tell it does a pretty decent job. It seems performant enough, and more importantly grants access to a Haskell-esque type system. This makes it a pretty good complement to Clojure for those problems where a strong typing system is important. The downside to Frege is that, even though documentation exists (and is actually quite expansive given the language's limited adoption), it's still hard to find straightforward how-tos by googling. So here's some much-needed frege-related blogspam to fill out those results. ## Target Joins the W3C DevFeed: [Target Joins the W3C]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2014-10-15T05:00:00Z Content type: release Language: en Sources: [Target]() Topics: [Web](), [Internet of things](), [Internet](), [coding-community]() Tags: [internet-of-things](), [location-based](), [open-source](), [standards](), [w3c](), [web](), [web-services]() ### AI overview Target announced its membership in the World Wide Web Consortium (W3C) and described plans to collaborate on web services, location-based content distribution, and the Internet of Things for retail-related technology. ### Source excerpt Tuesday, October 14th 2015, Target affirmed its commitment to technology and leadership in the retail space by joining the World Wide Web Consortium (W3C). As a company that cares about delivering great experiences for customers, we realize those experiences are now steeped in technology. One way Target can have a significant impact on shaping technology is open engagement with other companies and organizations at the heart of emerging development - the W3C enables us to do just that. So you joined - now what? There are so many areas of technology important to retail and associated businesses. Initially, we're interested in engaging with tech leaders, businesses, and organizations on web services, location-based content distribution (iBeacons, smart stores, etc.), and the Internet of Things. Through open dialogue and collaborative work in the W3C, we seek to push these areas of technology forward to enable new and better experiences for our customers. More to come soon! This is just the beginning. As an organization we will be engaging with the developer community in new and different ways, proposing ideas on the technologies that matter to us, and providing feedback of our progress. Now let's get to work! Target Joins the W3C was originally published by Target Brands, Inc at target tech on October 15, 2014. ## Using Go Client Worker Tasks to Scale Iron.IO Jobs DevFeed: [Using Go Client Worker Tasks to Scale Iron.IO Jobs]() Original publisher: [Read original article]() Published: 2013-12-20T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Scalability](), [Go Language](), [Architecture & Design](), [Programming]() Tags: [architecture](), [ardan-labs](), [blog](), [go](), [go-programming](), [golang](), [programming](), [queue](), [scalability](), [services](), [web-services]() ### AI overview This tutorial explains how to use Iron.IO worker tasks and its Go Client to queue independent jobs for scalable and redundant processing. It uses a marine forecast application as an example. ### Source excerpt Introduction The first thing I did when I started programming in Go was begin porting my Windows utilities classes and service frameworks over to Linux. This is what I did when I moved from C++ to C#. Thank goodness, I soon learned about Iron.IO and the services they offered. Then it hit me, if I wanted true scalability, I needed to start building worker tasks that could be queued to run anywhere at any time. It was not about how many machines I needed, it was about how much compute time I needed. ## Using Time, Timezones and Location in Go DevFeed: [Using Time, Timezones and Location in Go]() Original publisher: [Read original article]() Published: 2013-08-08T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [API](), [XML](), [DateTime](), [Google]() Tags: [api](), [ardan-labs](), [blog](), [code](), [data](), [developers](), [documentation](), [go](), [go-programming](), [golang](), [google](), [http](), [json](), [maps](), [programming](), [services](), [web-services]() ### AI overview This tutorial explains how to resolve local tide-station times to UTC in Go. It compares Google's Timezone API and GeoNames's timezone API, including their request requirements, response data, and stated usage considerations, then begins implementing a Google API call in Go. ### Source excerpt I ran into a problem today. I was building code to consume NOAA's tide station XML document and quickly realized I was in trouble. Here is a small piece of that XML document: LST/LDT 2013/01/01 Tue 19.7 600 H If you notice the timezone tag, it states the time is in Local Standard Time / Local Daylight Time. This is a real problem because I need to store this data in UTC. Without a proper timezone I am lost. After scratching my head for a bit my business partner showed me two API's that take a latitude and longitude position and return timezone information. Luckily for me I have a latitude and longitude position for each tide station. If you open this web page you can read the documentation for Google's Timezone API: External resource on developers.google.com: https://developers.google.com/maps/documentation/timezone/ The API is fairly simple. It requires a location, timestamps and a flag to identify if the requesting application is using a sensor, like a GPS device, to determine the location. Here is a sample call to the Google API and response: https://maps.googleapis.com/maps/api/timezone/json?location=38.85682,-92.991714&sensor=false×tamp=1331766000 { "dstOffset" : 3600.0, "rawOffset" : -21600.0, "status" : "OK", "timeZoneId" : "America/Chicago", "timeZoneName" : "Central Daylight Time" } There is a limit of 2,500 calls a day. For my initial load of the tide stations, I knew I was going to hit that limit and I didn't want to wait several days to load all the data. So my business partner found the timezone API from GeoNames. If you open this web page you can read the documentation for GeoNames's Timezone API: [http://www.geonames.org/export/web-services.html#timezone](/broken-link) The API requires a free account which is real quick to setup. Once you activate your account you need t ## Bill de hÓra on Choosing REST Over WS-\* Web Services DevFeed: [Bill de hÓra on Choosing REST Over WS-\* Web Services]() Original publisher: [Read original article]() Author: Graham King Published: 2007-11-17T02:59:45Z Content type: opinion Language: en Sources: [Graham King]() Topics: [Web]() Tags: [quote](), [services](), [software](), [web-services]() ### AI overview A quote attributed to Bill de hÓra criticizes advocates of WS-* style web services while contrasting them with REST-style services. ### Source excerpt There's no shortage of smart people digging the wrong hole really well Bill de hÓra, talking about advocates of the WS-* style web services, as opposed to REST style services.