What is Evernote's architecture these days? What might be surprising is that a year ago, it was still a monolith, with clients polling the servers! All of this is being rewritten behind the scenes. All of this is being changed:

Oct 24, 2024 · 9:01 AM UTC

5
6
2
82
0
Full episode with the team currently operating Evernote (Bending Spoons): newsletter.pragmaticengineer… On Spotify: open.spotify.com/show/2Bho9x… YouTube: piped.video/watch?v=6WM_q193…

Twisting the rules of building software: Bending Spoons (the team...

You may not be familiar with Bending Spoons, but I guarantee you’ve encountered some of their well-known products, like Evernote and Meetup. In today’s episo...

youtube.com
3
11
Replying to @GergelyOrosz
this is one of those things I guess: There's nothing inherently wrong with polling. It's simple, easy to implement, and works fine up to a certain scale.
1
3
Definitely one for scale, but also one for the speed of updates. 1. With polling you waste a lot more backend resources (typically) 2. With polling, updates to data depend on the frequency of the poll. Not ideal when you want to propagate it relatively quickly Agree it’s sensible to start like this. Uber worked like this till 2016! It was called “the ping” and was every 5 seconds I think? (Also these days much easier to implement data streamed to a device or web app)
1
8
more replies
Replying to @GergelyOrosz
It would be interesting to do a series of 20+ year old software products. How they are managed, maintained, refactored, etc. Or … not :) I am shocked how much of the copy of my last startup (Adobe Sign / EchoSign) has not changed since 2005
2
Replying to @GergelyOrosz
I remember playing around with WebSockets. It was pretty cool to see how the backend communicates with the frontend on its own.
2
Replying to @GergelyOrosz
Moving from monolith, is there a chance to understand how are they deciding which services to break out and distribute? I get the feeling they're headed towards hundreds of microservices, which could become a nightmare to manage eventually.
1
Load more