The public cloud has given enterprises a taste of infrastructure that is highly agile and scalable, that is deployed and managed by someone else and that can be paid for based on the resources use, and now they increasingly are looking for tech vendors to give them a similar experience with their on-premises and hybrid cloud environments. …
Today, as part of Crypto Week 2019, we are excited to announce Cloudflare's Ethereum Gateway, where you can interact with the Ethereum network without installing any additional software on your computer.
This is another tool in Cloudflare’s Distributed Web Gateway tool set. Currently, Cloudflare lets you host content on the InterPlanetary File System (IPFS) and access it through your own custom domain. Similarly, the new Ethereum Gateway allows access to the Ethereum network, which you can provision through your custom hostname.
This setup makes it possible to add interactive elements to sites powered by Ethereum smart contracts, a decentralized computing platform. And, in conjunction with the IPFS gateway, this allows hosting websites and resources in a decentralized manner, and has the extra bonus of the added speed, security, and reliability provided by the Cloudflare edge network. You can access our Ethereum gateway directly at https://cloudflare-eth.com.
This brief primer on how Ethereum and smart contracts work has examples of the many possibilities of using the Cloudflare Distributed Web Gateway.
Primer on Ethereum
You may have heard of Ethereum as a cryptocurrency. What you may not know is that Ethereum is so much more. Ethereum is a distributed virtual Continue reading
Today, we are excited to announce Cloudflare's Ethereum Gateway, where you can interact with the Ethereum network without installing any additional software on your computer.
This is another tool in Cloudflare’s Distributed Web Gateway tool set. Currently, Cloudflare lets you host content on the InterPlanetary File System (IPFS) and access it through your own custom domain. Similarly, the new Ethereum Gateway allows access to the Ethereum network, which you can provision through your custom hostname.
This setup makes it possible to add interactive elements to sites powered by Ethereum smart contracts, a decentralized computing platform. And, in conjunction with the IPFS gateway, this allows hosting websites and resources in a decentralized manner, and has the extra bonus of the added speed, security, and reliability provided by the Cloudflare edge network. You can access our Ethereum gateway directly at https://cloudflare-eth.com.
This brief primer on how Ethereum and smart contracts work has examples of the many possibilities of using the Cloudflare Distributed Web Gateway.
Primer on Ethereum
You may have heard of Ethereum as a cryptocurrency. What you may not know is that Ethereum is so much more. Ethereum is a distributed virtual computing network that stores and enforces smart Continue reading
When we launched our InterPlanetary File System (IPFS) gateway last year we were blown away by the positive reception. Countless people gave us valuable suggestions for improvement and made open-source contributions to make serving content through our gateway easy (many captured in our developer docs). Since then, our gateway has grown to regularly handle over a thousand requests per second, and has become the primary access point for several IPFS websites.
We’re committed to helping grow IPFS and have taken what we have learned since our initial release to improve our gateway. So far, we’ve done the following:
Automatic Cache Purge
One of the ways we tried to improve the performance of our gateway when we initially set it up was by setting really high cache TTLs. After all, content on IPFS is largely meant to be static. The complaint we heard though, was that site owners were frustrated at wait times upwards of several hours for changes to their website to propagate.
The way an IPFS gateway knows what content to serve when it receives a request for a given domain is by looking up the value of a TXT record associated with the domain – the DNSLink Continue reading
SD-WAN is the best thing that could have happened to networking according to some industry “thought leaders” and $vendor marketers… but it seems there might be a tiny little gap between their rosy picture and reality.
This is what I got from someone blessed with hands-on SD-WAN experience:
It’s hard to define good SLOs, especially when outcomes aren’t fully under the control of any single party. The authors of today’s paper should know a thing or two about that: Jeffrey Mogul and John Wilkes at Google1! John Wilkes was also one of the co-authors of chapter 4 “Service Level Objectives” in the SRE book, which is good background reading for the discussion in this paper.
The opening paragraph of the abstract does a great job of framing the problem:
Cloud customers want strong, understandable promises (Service Level Objectives, or SLOs) that their applications will run reliably and with adequate performance, but cloud providers don’t want to offer them, because they are technically hard to meet in the face of arbitrary customer behavior and the hidden interactions brought about by statistical multiplexing of shared resources.
When it comes to SLOs, the interests of the customer and the cloud provider are at odds, and so we end up with SLAs (Service Level Agreements) that tie SLOs to contractual agreements.
What are we talking about
Let’s start out by getting some terms straight: SLIs, SLOs, SLAs, and Continue reading
Many times when I visited various conferences or had meetings with vendors, I was confused by the naming conventions of the roles they have. System engineer, pre-sales, account manager, etc… If you feel the same, watch this video!
CY2019 Episode 3 // The enginnering jobs in the vendors with Ahmed Elbornou
In this episode, together with Ahmed Elbornou from Juniper we discuss the typicall journey of the product within the company (like router, or SW product) and how various technical roles contribute to its creation
Don’t forget to subscribe for the channel, put likes and repost the video if you like that!
Support us
P.S.
If you have further questions or you need help with your networks, I’m happy to assist you, just send me message. Also don’t forget to share the article on your social media, if you like it.
Let’s go more into depth what the new updates really mean. We will start by analyzing the CCNA. As I described in the previous post, gone are the days of having 11 different tracks, instead there is 1 exam. Why?
Take a second to think about what you expect from a Junior Network Engineer, that is after all what a CCNA is expected to be. I, probably Russ White, and many other with me, would argue that what is important at any level, but certainly as a junior, is to understand the fundamentals well. That is to know binary, subnetting, supernetting, basic TCP/IP, basic routing and switching, a little about wireless, a little about security. You don’t need to specialize at a junior level. Many athletes do several sports until they have to pick one and studies have shown that this is often has a positive effect compared to focusing on a single one too soon.
The change in the CCNA is therefore to better align with the expected job role of a CCNA. What domains are being tested? The domains being tested are:
Modern applications can come in many flavors, consisting of different technology stacks and architectures, from n-tier to microservices and everything in between. Regardless of the application architecture, the focus is shifting from individual containers to a new unit of measurement which defines a set of containers working together – the Docker Application. We first introduced Docker Application packages a few months ago. In this blog post, we look at what’s driving the need for these higher-level objects and how Docker Enterprise 3.0begins to shift the focus to applications.
Scaling for Multiple Services and Microservices
Since our founding in 2013, Docker – and the ecosystem that has thrived around it – has been built around the core workflow of a Dockerfile that creates a container image that in turn becomes a running container. Docker containers, in turn, helped to drive the growth and popularity of microservices architectures by allowing independent parts of an application to be turned on and off rapidly and scaled independently and efficiently. The challenge is that as microservices adoption grows, a single application is no longer based on a handful of machines but dozens of containers that can be divided amongst different development teams. Continue reading
Lyra is the latest infrastructure-as-code project to tackle the provisioning of cloud resources. On today's Full Stack Journey, guest and Lyra contributor Eric Sorenson explains how Lyra works, how it competes with and complements Terraform, and what it does differently from other open-source options.
Lyra is the latest infrastructure-as-code project to tackle the provisioning of cloud resources. On today's Full Stack Journey, guest and Lyra contributor Eric Sorenson explains how Lyra works, how it competes with and complements Terraform, and what it does differently from other open-source options.
Being #1 has its own kind of pressure. When you’re #2 in the market you have a clear goal: topple the #1. What’s the mindset of a market leader? Watch your back? Protect what you have? Ignore everything?
Harel lnsurance lnvestments & Financial Services is the leader of Israel’s insurance market. It has four big rivals competing for its business and must be conscious of outside disruptors turning the market on its head. An understandable strategy might be for Harel to sit tight and protect what it has.
Instead, Harel wants to transform its entire approach. It doesn’t just want to be big, it wants to be fast. It wants to succeed by being the first to launch new services, by exploring new forms of customer engagement, by being innovative.
Harel, formed through a series of mergers and acquisitions, wants to:
Create an efficient, flexible IT infrastructure to support its entire operation
Automate human process, shifting IT’s focus from maintenance to new service development
Remove barriers to storage, performance and network, allowing developers to be faster to market with new services
IT will become the ‘silent leader’ of change throughout the business, proactively steering Continue reading