url - Best folder structure for assets/images of a social networking web and mobile application -
i wondering rationale behind big social networks folder structures images hold. i'm creating api smaller social app endpoints similar following:
https://api.example.com/v1/users/<id> https://api.example.com/v1/users/<id>/posts/<post_id>
and users can upload profile images via put
call to:
https://api.example.com/v1/users/<id>/images
now images served through nginx , example can access profile image via:
https://cdn.example.com/images/user/<id>/profile/<imagename>.jpg
so i'm wondering why facebook, twitter, instagram , guys have structures similar giberish:
https://fbcdn-photos-d-a.akamaihd.net/hphotos-ak-xal1/v/t1.0-0/p480x480/10329215_977076969053738_7417509963714441891_n.jpg?oh=64aecaca7a84139c16e8a0f579782034&oe=57880bf0&__gda__=1469390211_f894185cc7e133738a0b9321e28e53c3
i'm aware have insane levels of images serve , across many servers, can't make sense of urls.
Comments
Post a Comment