blog.frankel.ch/backend-for-frontend
Preview meta tags from the blog.frankel.ch website.
Linked Hostnames
12- 13 links toblog.frankel.ch
- 2 links tobsky.app
- 2 links totwitter.com
- 2 links towww.reddit.com
- 1 link todocs.microsoft.com
- 1 link togithub.com
- 1 link tomastodon.top
- 1 link tosamnewman.io
Thumbnail

Search Engine Appearance
Discussing Backend For Front-end
In the good old days, applications were simple. A browser sent a request to a webapp endpoint; the latter fetched data from a database and returned the response. The rise of mobile clients and integrations with other apps upset this simplicity. I want to discuss one solution to handle the complexity in this post. The increased complexity of system architecture Let’s first model the above simple architecture. Mobile clients changed this approach. The display area of mobile clients
Bing
Discussing Backend For Front-end
In the good old days, applications were simple. A browser sent a request to a webapp endpoint; the latter fetched data from a database and returned the response. The rise of mobile clients and integrations with other apps upset this simplicity. I want to discuss one solution to handle the complexity in this post. The increased complexity of system architecture Let’s first model the above simple architecture. Mobile clients changed this approach. The display area of mobile clients
DuckDuckGo
Discussing Backend For Front-end
In the good old days, applications were simple. A browser sent a request to a webapp endpoint; the latter fetched data from a database and returned the response. The rise of mobile clients and integrations with other apps upset this simplicity. I want to discuss one solution to handle the complexity in this post. The increased complexity of system architecture Let’s first model the above simple architecture. Mobile clients changed this approach. The display area of mobile clients
General Meta Tags
9- titleDiscussing Backend For Front-end
- charsetutf-8
- X-UA-CompatibleIE=edge
- HandheldFriendlytrue
- viewportwidth=device-width, initial-scale=1.0
Open Graph Meta Tags
8- og:site_nameA Java geek
- og:typewebsite
- og:titleDiscussing Backend For Front-end
- og:descriptionIn the good old days, applications were simple. A browser sent a request to a webapp endpoint; the latter fetched data from a database and returned the response. The rise of mobile clients and integrations with other apps upset this simplicity. I want to discuss one solution to handle the complexity in this post. The increased complexity of system architecture Let’s first model the above simple architecture. Mobile clients changed this approach. The display area of mobile clients
- og:urlhttps://blog.frankel.ch/backend-for-frontend/
Twitter Meta Tags
7- twitter:cardsummary_large_image
- twitter:site:idnicolas_frankel
- twitter:titleDiscussing Backend For Front-end
- twitter:descriptionIn the good old days, applications were simple. A browser sent a request to a webapp endpoint; the latter fetched data from a database and returned the response. The rise of mobile clients and integrations with other apps upset this simplicity. I want to discuss one solution to handle the complexity in this post. The increased complexity of system architecture Let’s first model the above simple architecture. Mobile clients changed this approach. The display area of mobile clients
- twitter:urlhttps://blog.frankel.ch/backend-for-frontend/
Item Prop Meta Tags
10- nameNicolas Fränkel
- givenNameNicolas
- familyNameFränkel
- jobTitleHead of Developer Advocacy
- worksForApache APISIX
Link Tags
12- alternatehttps://blog.frankel.ch/feed.xml
- urlhttps://blog.frankel.ch/backend-for-frontend/
- mehttps://mastodon.top/@frankel
- mehttps://github.com/nfrankel
- shortcut icon/assets/cup.ico
Links
27- http://www.reddit.com/submit?url=https://blog.frankel.ch/backend-for-frontend/&title=Discussing Backend For Front-end
- https://blog.frankel.ch
- https://blog.frankel.ch/backend-for-frontend-demo
- https://blog.frankel.ch/books
- https://blog.frankel.ch/feed.xml