Hi,
I'm now researching how to globalize web services suitably, and I want to find out as many possible problems on globalizing web services as possible.
Have you faced any problems (not only technical but also cultural, religious, linguistic, etc.) when you are developing web services targeting global audiences? If so, how did you solve them?
Top comments (2)
Ooh great question. I'm busy now but I'm going to try to get back to this.
I look forward to reading other responses.
Okay I'll add some things:
The biggest hurdle is not really being totally sure what the right thing to do in various situations. There are just a lot of different things to get right and it's hard to know where to start.
This thread was helpful: dev.to/ben/what-do-american-develo...
We've consistently had some paralysis by analysis with everything. We're still not that internationalized, but we've tried to avoid major pitfalls.
But from the get we really wanted to be fast all around the world. So that's been our main form of internationalization. Every corner of the globe should get a pretty fast site. This is not true for many websites.
This also makes it slightly harder to do some of the aforementioned things we could be doing for internationalization because a lot of our logic lives on the edge with our CDN Fastly.
Just a few thoughts @chooyan hope it helps.