Postumius Suagrus Praefectus urbi | Bibliographia | Notae | Tabula navigationis

Nati saeculo 2 aut 3SenatoresGens PostumiaPraefecti urbi Romae antiquiMortui saeculo 3 aut 4


275praefectus urbi Romae




Postumius Suagrus (nescimus, quando natus mortuusve sit) senator Romanus saeculi tertii fuit.



Praefectus urbi |


Suagrus anno 275 praefectus urbi Romae erat[1]. Nihil praeterea de eo novimus.



Bibliographia |


  • Martindale, J. R.; Jones, A. H. M, The Prosopography of the Later Roman Empire, Vol. I AD 260-395, Cambridge University Press (1971)


Notae |



  1. ↑ Chronographus anni 354, 10








Popular posts from this blog

Saint-André (Pyrenaeus Orientalis) Nexus interni Nexus externi | Tabula navigationisOpenStreetMapGeoNames66168De hoc commune apud cassini.ehess.frHuius communis pagina interretialisAmplifica

Remove specific words in a stringWhat is the difference between String and string in C#?How do I iterate over the words of a string?How do I read / convert an InputStream into a String in Java?Extract filename and extension in BashHow to replace all occurrences of a string in JavaScriptHow to check whether a string contains a substring in JavaScript?Does Python have a string 'contains' substring method?How do I check if a string contains a specific word?How do I convert a String to an int in Java?Why is char[] preferred over String for passwords?

Does splitting a potentially monolithic application into several smaller ones help prevent bugs?Problem with understanding “seam” wordApplications Architecture - fewer big systems vs more smaller systemsMicro vs Monolithic Server architectureSeparating Code into Smaller Files in CDesign, how to utilize The Hardware (multiple threads and/or GPU) while indexing (via a database) a very large set of binary filesWhich approach should I use to split a monolithic application into several microservices?Is there a standard for documenting a program's high-level architecture?Relative merits of monolithic repository over multiple smaller onesmany sub application or a big oneWhere to store data for Microservices Architecture?Splitting application into multiple but keeping database same