Really, you are getting something of great value for free in return for your e-mail, and feel obligated to try and contort and "screw" them? This is the exact sort of mentality that frustrates me as an entrepreneur. If you don't like the terms, then simply hit back. You're not entitled to anything. end of rant
I’m an enterprise architect in a place which operates more than 500 different IT systems. I’m on the receiving end of the kind of things this signup will lead to, a lot, really you have no idea how many times I’m contacted.
It’s completely anecdotal but contacting me the way nginx and parters will after I’ve received the free ebook will only do them harm. My department has never taken anyone up on the offerings, and if they don’t include a working unsubscribe link, then you end up blocked companywide.
The free ebook is a lot of good will though, and I’ll remember where it came from. So if it’s good it was a much better investment than whatever usage they’ll get from my email.
His email is available on his profile, so he essentially already shared it for free...
I agree that it's not exactly free because it has a value, just like your comment right now has one. However it doesn't represent a monetary loss from you (just like your comment right now), which I believe is what he meant by free.
If you believe your personnal email and phone number has a value higher than this ebook, than yeah, don't exchange them, that would be absurd.
Well he put his email in a not so easily readable format in there, so someone has to take effort and invest time to generate a correct email address from it. With this time investment getting to the email address costs money. So not for free ;)
But of course now we are definitely nitpicking on a philosophical level.
My point basically if someone says something is free, but requests your personal data in return, then that is not free.
> Really, you are getting something of great value for free in return for your e-mail
No, I am not getting it as “free”. That’s misleading at best and I personally think it’s disingenuous. We need to call out the cost of personally identifiable information.
Instead of getting frustrated, say you’re giving the information (book in this case) for the cost of being able to hold your personally identifiable email address for X period of time for Y purpose.
It’s not “free”, let your audience know and advertise it so.
Yet another JavaScript heavy and so flakey form to implement a basic task. So tried to provide details but it did not work. So I am grateful for the link.
You have an issue with people taking companies at their word and providing ways to get things for free just as they claimed it would be?
As I said in the other comment, everyone can value their contact information themselves, but I guess that most people value them >0. And >0 is not free, otherwise the company would not have any reason to get them.
Step 2: completely transform your existing organization to be a matrix of agile teams with chargeback budgets aligned to resource use of shared services and collaborating on product lifecycles in scrum and kanban using full test coverage on both legacy and modern apps stored in asset-managed Docker containers in ci/cd pipelines triggered by Jira tickets deploying declarative immutable infrastructure and integrating an array of site reliability services that don't ship with k8s while adding policy and compliance enforcement with secret management and process auditing including in-line content filters using redundant services in multiple data centers without wasting resources or money
I absolutely loved the concept of containerization when I started working with it a few years ago. Docker provided such a perfect way to ensure my application would build and run correctly when I pushed things up to my servers.
Then came orchestration. Swarm was a bit slow to get out the door and is still buggy. K8s on the other hand shot past like a lightning bolt. While it evolved quickly, k8s has to be the one piece of software that I dread to work with the most. Setting up a cluster seems nearly impossible without compromising important features. Configuration is overly complex and difficult to discover. None of the (many) tools seem to do what I want.
In the end, I begrudgingly chose Docker Swarm because I was actually able to create a cluster that worked. Mind you, there are still truckloads of bugs that have sat gathering dust for years that I continue to run into. At least with this solution I'm somewhat productive.
May the heavens have mercy on your soul should you attempt any amount of networking in a cluster.
Kubernetes is hard because its trying to solve a hard problem. Agreed that cluster management itself is hard but GKE has been somewhat nicer to use.
If you can convince your organization to use GKE (Google Kubernetes Engine), your life will become simpler. Power of Kubernetes with none (almost!) of the pain.
> Kubernetes is hard because its trying to solve a hard problem.
Yeah, and for most of us it's a problem we don't actually have.
Use of these technologies seems aspirational to me. It's a kind of cargo-culting: as if using the methods of the software giants, will make your company into a software giant.
That's the problem I have with it. I'm supposed to fight with all this extra infrastructure and configuration...to deploy a standard php web app with 600 users.
If you have very simple use cases, you definitely do not need an orchestrator, or a cluster. The hype is too loud and pretends to be good for everyone when it's clearly not.
I want to coin a new term "SimpleOps": operations infrastructure which does not include complex components such as cluster orchestrators, service meshes, secret management, IAM, policy enforcement, telemetry processing engines, app tracing, and so on. If your app is simple, only use simple components and managed services.
You can still have DevOps best practices with very simple components, and it'll be easier to reason about, build, and run.
I would like to, but I don't really have a choice atm. Thanks for the advice though, I feel like it doesn't need to be super complex to do what we're doing.
I generally use k8s. The updates come like a torrent, and it's impossible to stay on top of things unless it's your full time job. Every upgrade involves a lot of finger-crossing and hope that things won't break (the good news is, that generally it's fine).
The sheer length of the sentence and the variety in vocabulary creates a rising, racing energy that forces you to stop and smile before you get to the end.
Beautifully written! I’m going to save a copy for myself.
That said, I'm running a few GKE clusters now with an 18-month old production codebase, and its kind of been a pleasure. That's a good portion of a million dollars in my pocket, no matter how the start-up fares after its done ;-)
Business email, company, job title — what if someone doesn't have one or more of these? I know one can give fake information, but why are all the fields on the form marked with an asterisk indicating that they're mandatory? It's asking for phone number too?! Thanks, but no thanks. This is not for me.
Im glad its an eBook, not a book.
Since I work in tech, I am excited that its a eBook that I can search through easily rather than having to spend tons of time bookmarking and flipping through pages hoping to find what is relevant when I need it. Paper books have some novelty value but I much prefer the utility of full text search when its time to get something done.
Really? I like ebooks for novel style format, but for technical books - where I don't necessarily them read in a linear manner - I find them way worse to browse.
Kubernetes is an overkill for 90% of systems. The hype will die off eventually, but not before ruining fair number of projects. Death by overengineering. I wonder how things even worked before containers :)
I don't have hands on experience with kubernetes and a quite a bit skeptical because of its supposed complexity. Would be interested in success stories though where kubernetes magic was the much needed secret sauce.
I used a disposable email service to receive the ebook. This is the permalink to the attached ebook: https://rainmail.xyz/attachments/nginx@filerpost.xyz/143/Clo...
https://cgateu03maus.storage-mailcom.com/cgate-maus/rest/doc...
Thanks, did try to fill the form out but it wouldn't submit.
Really, you are getting something of great value for free in return for your e-mail, and feel obligated to try and contort and "screw" them? This is the exact sort of mentality that frustrates me as an entrepreneur. If you don't like the terms, then simply hit back. You're not entitled to anything. end of rant
I’m an enterprise architect in a place which operates more than 500 different IT systems. I’m on the receiving end of the kind of things this signup will lead to, a lot, really you have no idea how many times I’m contacted.
It’s completely anecdotal but contacting me the way nginx and parters will after I’ve received the free ebook will only do them harm. My department has never taken anyone up on the offerings, and if they don’t include a working unsubscribe link, then you end up blocked companywide.
The free ebook is a lot of good will though, and I’ll remember where it came from. So if it’s good it was a much better investment than whatever usage they’ll get from my email.
Well the value of personal contact data can everyone decide on their own, but personally I would not rate that as free.
If you think your contact data (personal email and phone number) has no value, please share them here. You will probably get great value from it!
His email is available on his profile, so he essentially already shared it for free...
I agree that it's not exactly free because it has a value, just like your comment right now has one. However it doesn't represent a monetary loss from you (just like your comment right now), which I believe is what he meant by free.
If you believe your personnal email and phone number has a value higher than this ebook, than yeah, don't exchange them, that would be absurd.
Well he put his email in a not so easily readable format in there, so someone has to take effort and invest time to generate a correct email address from it. With this time investment getting to the email address costs money. So not for free ;)
But of course now we are definitely nitpicking on a philosophical level.
My point basically if someone says something is free, but requests your personal data in return, then that is not free.
At some point entrepreneurs need to run into the fact their business model wont work.
Any effort to control the distribution of digital media on the internet is doomed to fail. It is not our job to prop up failed business models.
or should we just give you money because we feel sorry for you not realizing this ?
> Really, you are getting something of great value for free in return for your e-mail
No, I am not getting it as “free”. That’s misleading at best and I personally think it’s disingenuous. We need to call out the cost of personally identifiable information.
Instead of getting frustrated, say you’re giving the information (book in this case) for the cost of being able to hold your personally identifiable email address for X period of time for Y purpose.
It’s not “free”, let your audience know and advertise it so.
Yet another JavaScript heavy and so flakey form to implement a basic task. So tried to provide details but it did not work. So I am grateful for the link.
EOR
Well unless you plan to read their future marketing emails you've "screwed" them anyway, leaving the email or not.
That's the feeling I have reading every single comment around here lately.
You have an issue with people taking companies at their word and providing ways to get things for free just as they claimed it would be?
As I said in the other comment, everyone can value their contact information themselves, but I guess that most people value them >0. And >0 is not free, otherwise the company would not have any reason to get them.
Access denied!!
https://ipfs.io/ipfs/QmYseupfjUd2fCxdikbo1CuAUvbg3oqbxAD3awj...
Upvote for IPFS. Pinned the resource on my node to spread out the load, thanks!
Yeah, it seems it got deleted. I switched to another disposable email provider, you can check again the link.
You saved a lot of Nginx money and cloud resources. They won't be sending newsletter to some 10minutes or spam only mailboxes.
Step 1: implement Kubernetes
Step 2: completely transform your existing organization to be a matrix of agile teams with chargeback budgets aligned to resource use of shared services and collaborating on product lifecycles in scrum and kanban using full test coverage on both legacy and modern apps stored in asset-managed Docker containers in ci/cd pipelines triggered by Jira tickets deploying declarative immutable infrastructure and integrating an array of site reliability services that don't ship with k8s while adding policy and compliance enforcement with secret management and process auditing including in-line content filters using redundant services in multiple data centers without wasting resources or money
Step 3: document it
(I haven't read the book yet, so ymmv)
You're joking but it's almost too accurate to be humorous. This is being foisted on us right now and it's giving me nearly crippling anxiety.
I absolutely loved the concept of containerization when I started working with it a few years ago. Docker provided such a perfect way to ensure my application would build and run correctly when I pushed things up to my servers.
Then came orchestration. Swarm was a bit slow to get out the door and is still buggy. K8s on the other hand shot past like a lightning bolt. While it evolved quickly, k8s has to be the one piece of software that I dread to work with the most. Setting up a cluster seems nearly impossible without compromising important features. Configuration is overly complex and difficult to discover. None of the (many) tools seem to do what I want.
In the end, I begrudgingly chose Docker Swarm because I was actually able to create a cluster that worked. Mind you, there are still truckloads of bugs that have sat gathering dust for years that I continue to run into. At least with this solution I'm somewhat productive.
May the heavens have mercy on your soul should you attempt any amount of networking in a cluster.
Kubernetes is hard because its trying to solve a hard problem. Agreed that cluster management itself is hard but GKE has been somewhat nicer to use.
If you can convince your organization to use GKE (Google Kubernetes Engine), your life will become simpler. Power of Kubernetes with none (almost!) of the pain.
> Kubernetes is hard because its trying to solve a hard problem.
Yeah, and for most of us it's a problem we don't actually have.
Use of these technologies seems aspirational to me. It's a kind of cargo-culting: as if using the methods of the software giants, will make your company into a software giant.
That's the problem I have with it. I'm supposed to fight with all this extra infrastructure and configuration...to deploy a standard php web app with 600 users.
If you have very simple use cases, you definitely do not need an orchestrator, or a cluster. The hype is too loud and pretends to be good for everyone when it's clearly not.
I want to coin a new term "SimpleOps": operations infrastructure which does not include complex components such as cluster orchestrators, service meshes, secret management, IAM, policy enforcement, telemetry processing engines, app tracing, and so on. If your app is simple, only use simple components and managed services.
You can still have DevOps best practices with very simple components, and it'll be easier to reason about, build, and run.
I would like to, but I don't really have a choice atm. Thanks for the advice though, I feel like it doesn't need to be super complex to do what we're doing.
I generally use k8s. The updates come like a torrent, and it's impossible to stay on top of things unless it's your full time job. Every upgrade involves a lot of finger-crossing and hope that things won't break (the good news is, that generally it's fine).
Step 2 in your comment reads like poetry.
The sheer length of the sentence and the variety in vocabulary creates a rising, racing energy that forces you to stop and smile before you get to the end.
Beautifully written! I’m going to save a copy for myself.
He must be a PR/marketing guy
Nah, he did not use "leverage" or "synergy".
More like someone burned well and truly..
"It takes well over a million dollars just in engineer salary to get k8s up and running from scratch. And you still might not get there." - Cindy Sridharan[1](https://twitter.com/copyconstruct/status/1020880388464377856...)
That said, I'm running a few GKE clusters now with an 18-month old production codebase, and its kind of been a pleasure. That's a good portion of a million dollars in my pocket, no matter how the start-up fares after its done ;-)
[1][https://twitter.com/copyconstruct/status/1020880388464377856...
Step 4: audit controls against FFIEC and NIST
Step 5: begin remediation to remove suspiciously hands-off automations that a few dozen humans could do and check manually instead
Step 6: lift and shift another past due application into your old hyperconverged private cloud because ITIL is looking pretty good right now
Step 7: git pull upgraded K8s, go to Step 1
/s (typical enterprise IT allergic reaction)
You forgot the new and interesting bugs that come with k8s / docker
Bad Bus Ride on the K8S
Business email, company, job title — what if someone doesn't have one or more of these? I know one can give fake information, but why are all the fields on the form marked with an asterisk indicating that they're mandatory? It's asking for phone number too?! Thanks, but no thanks. This is not for me.
This looks like a job for Mr Fake McFakeFake, CFO[•], Fake Enterprises, New Faketon, Fakeshire.
[•] Chief Fakery Officer
Also forced consent
agreed.
"Free*
...
...
* not really"
> This is not for me.
I don't recall last time I've put real info in these forms. Protonmail worked just fine.
Its an eBook, not a book.
Even though I work in tech, I was excited that they were giving a way a print copy I could flick though easily, and bookmark, annotate or share.
EBooks have some advantages, but I still prefer print.
Im glad its an eBook, not a book. Since I work in tech, I am excited that its a eBook that I can search through easily rather than having to spend tons of time bookmarking and flipping through pages hoping to find what is relevant when I need it. Paper books have some novelty value but I much prefer the utility of full text search when its time to get something done.
Really? I like ebooks for novel style format, but for technical books - where I don't necessarily them read in a linear manner - I find them way worse to browse.
TBH the index feels well-curated. It’s not one of those cases when you have hundreds of pages just tied together in a pdf.
https://imgur.com/a/BPNCBnp
Likewise. Physical books simply lack the Ctrl+F key combo.
Ctrl + F feels like going to the index and looking something up. In that case its faster with an ebook.
However scrolling through / flipping through pages to find something feels much more effective with a real book.
honestly, same for me. i really like to write on technical books (i know, i know) and highlight parts.
i tried doing the same with pdfs... and it's just not the same thing.
You can just get it printed and bound. O'Reilly's PDFs are not protected or hindered any way to discourage printing.
Check out getpolarized.io it enables bookmarking and even exporting to anki
Nginx is giving away an ebook with email newsletter subscription.
And also to use your email address to target you with advertising.
Expect to see lots of Nginx ads on Facebook, Twitter etc.
I’d rather see nginx ads than the ones I usually see to be honest.
Here's a lengthy interview with John Arundel, an author of the book: https://semaphoreci.com/blog/2019/02/14/a-reality-check-abou... You can get a lot from it without giving away any of your personal or fake information. :)
Is this a proper ebook or one of those bullshit O'Reilly leaflets focused on a particular technology?
Actual book. 344 pages.
Sadly only in PDF format as far as I can tell.
Needs a form fill with a valid email, but it really is the full just-released 300+ page book.
...and name, work, phone number, and requires consent to receive emails from nginx...
...easiest free content of my life...
Got a link?
I'm sure you can put in the work to fill the form with some made up info if you really want the book.
... none of which needs to be real :)
Why are half the comments complaining about giving name and email? Thanks for sharing this!
They thought it was free.
I’m sad they didn’t get what the expected, but happy that there are still groups of people getting on the internet for the first time.
Well if I don't pay and only fill a form, it seems free to me.
That's the trick.
"in exchange of your identity"
can't we stop calling confusing this with "free"?
Forcing you to give consent to receive a newsletter in order to download the ebook is not the way to go
Nobody is forcing you. You don't have to fill the form if you don't want. Exchanging the book for your email seems a fair deal to me.
Do you expect them to get nothing in return?
That's the traditional definition of "free" (as in beer).
Example code that goes with the book is also freely available:
https://github.com/cloudnativedevops/demo
Kubernetes is an overkill for 90% of systems. The hype will die off eventually, but not before ruining fair number of projects. Death by overengineering. I wonder how things even worked before containers :)
What are some example where you think Kubernetes is the right choice?
When you have to run many different apps from 3rd party devs, having standard deployment format helps. Or on-demand apps, like ETL jobs.
Containers offer not much benefit if you're cloud native - you already have VMs and heaps of automation APIs.
Google, Facebook, AOL , Oath/Y!
When you have a large scale platform with millions of users and you need to add / remove / change services at some marketing teams whim
Do they run on kubernetes though?
Google runs on its own container system, Borg. Kubernetes is a free reimplementation of Borg sponsored by Google.
So one of them rounded up?
I don't have hands on experience with kubernetes and a quite a bit skeptical because of its supposed complexity. Would be interested in success stories though where kubernetes magic was the much needed secret sauce.
https://news.ycombinator.com/item?id=18953647
Hopfully this ebook can help those who want to build modern applications in the cloud.
Regard Writer on https://www.tolongtangtugas.web.id
i will not read an o'riley book if you paid me to do it