praxis | Convox Praxis : A framework for modern application

You could do the following:

The html you posted is broken. You have html tags inside incomplete comments. Everything after
0.3 km

Am Rathausplatz 4
33014 Bad Driburg

""" soup = BeautifulSoup(html, 'lxml') # if you use html.parser the code below will be different # find element first, then get text element next to it addressLine1 = str(soup.find('img', class_='').findNextSibling(text=True).findNextSibling(text=True).findNextSibling(text=True)).strip() # Am Rathausplatz 4 addressLine2 = str(soup.find('img', class_='').findNextSibling(text=True).findNextSibling(text=True).findNextSibling(text=True).findNextSibling(text=True)).strip() # 33014 Bad Driburg print(addressLine1) print(addressLine2)

I don't see why there would be a duplicate as there is only one instance of the href tag with a class of "it" in your example source. I'm unclear if you're trying to extract the "0 52 53 / 65 65" or the "tel:+4952536565" but in both cases you could do:

Build a regular expression pattern from the list of search words. I have assumed these are in column A on sheet 2 starting at row 1.

It's totally dependent on the requirement and how you design. My opinion is that if you using function components you don't need to mix with class components and bind(this).

Note: WithDashboard function you are not passing props if any component passes props that are not passed to WithDashboardBase.

You could use the following regex (?<=\[\[)([\w\s]+)(?=]])|(\w+) which is of the way firstWay|secondWay, the | is an OR

1. (?<=\[\[)([\w\s]+)(?=]]) which means

   • ([\w\s]+) : characters or spaces, so can be a list of words
   • (?<=\[\[) ensure that is prefixed by 2 oppening square brackets
   • (?=]]) ensure that is prefixed by 2 closing square brackets

2. (\w+) is just a word

Giving

If your application is hosted in a region e.g. eu-west-1 the best read performance will always come when it is reading data from eu-west-1.

If you happen to have customers in us-east-1 you have to choose between one of 3 options:

Edge Location

You reduce the latency using edge locations, i.e. CloudFront or Global Accelerator. This will improve the latency by using the AWS Backbone to route to your origins. This is faster than previously but the application remains in the original region (in this case eu-west-1). You also maintain one copy of the application only.

Latency based routing

This option brings the application closer to the user, by using either Route 53 with latency based records or Global Accelerator you can have your domains resolve to the location that has the lowest latency for them. You would have your central region (where the readwrite lives) and then create cross region replicas. This will provide the best read performance as the reads are being done locally (rather than being across region).

In the example eu-west-1 is the primary region with cross region replicas in us-east-1. Latency between regions is only observed with the time it takes to write to the readwrite (in the original region unless you use Aurora Read Replica Write Forwarding). This is by far the most complex and costly, but will provide the best performance overall.

Do nothing

If you do nothing this option will use the public internet to route to a host, those who are further away to your application will have a longer latency, but this is the cheapest option.

Summary

You need to essentially decide on the importance of cross region, if it is simply because your user base is in a further away region then ensuring you're as close to them as possible is key. You would not need to think about replicas if you're in a specific geographical region.

Remember you can always enhance your infrastructure when demand increases from other geographical regions.

Using your exact filter criteria would this do it?