by 100 věcí, které by každý programátor měl znát
Podcast vznikl za účelem rozšiřovat obzory a přinášet nové vědomosti lidem, kteří se pohybují v IT. S hosty probereme do hloubky určitou technologii. Pokud máte zájem se zúčastnit podcastu jako host, kontaktujte mě na email [email protected].
Language
🇨🇿
Publishing Since
10/24/2021
Email Addresses
1 available
Phone Numbers
0 available
March 18, 2024
<p>A codebase is transformed into a (non-development) deploy through three stages:<br>The build stage is a transform which converts a code repo into an executable bundle known as a build. Using a version of the code at a commit specified by the deployment process, the build stage fetches vendors dependencies and compiles binaries and assets.<br>The release stage takes the build produced by the build stage and combines it with the deploy’s current config. The resulting release contains both the build and the config and is ready for immediate execution in the execution environment.<br>The run stage (also known as “runtime”) runs the app in the execution environment, by launching some set of the app’s processes against a selected release.</p>
March 8, 2024
<p>A <em>backing service</em> is any service the app consumes over the network as part of its normal operation. Examples include datastores (such as <a href="http://dev.mysql.com/">MySQL</a> or <a href="http://couchdb.apache.org/">CouchDB</a>), messaging/queueing systems (such as <a href="http://www.rabbitmq.com/">RabbitMQ</a> or <a href="https://beanstalkd.github.io/">Beanstalkd</a>), SMTP services for outbound email (such as <a href="http://www.postfix.org/">Postfix</a>), and caching systems (such as <a href="http://memcached.org/">Memcached</a>).</p> <p>Backing services like the database are traditionally managed by the same systems administrators who deploy the app’s runtime. In addition to these locally-managed services, the app may also have services provided and managed by third parties. Examples include SMTP services (such as <a href="http://postmarkapp.com/">Postmark</a>), metrics-gathering services (such as <a href="http://newrelic.com/">New Relic</a> or <a href="http://www.loggly.com/">Loggly</a>), binary asset services (such as <a href="http://aws.amazon.com/s3/">Amazon S3</a>), and even API-accessible consumer services (such as <a href="http://dev.twitter.com/">Twitter</a>, <a href="https://developers.google.com/maps/">Google Maps</a>, or <a href="http://www.last.fm/api">Last.fm</a>).</p>
July 24, 2023
<p>V podcastu "DevOps vs. SRE" se podíváme pod pokličku do firem SentinelOne a Pipedrive a to s ohledem na následující témata:<br>- Přechod z on-premises do cloudu<br>- Cloudové výhody, nevýhody a šetření peněz<br>- Ownership a cost management:<br>- Release proces, testování a nasazení do produkce<br>- Observabilita<br>Hosty:<br>Kryštof Matějka, Pipedrive - <a href="https://www.linkedin.com/in/krystof-matejka/" target="_blank">https://www.linkedin.com/in/krystof-matejka/</a><br>Richard Fojta, SentinelOne - <a href="https://www.linkedin.com/in/richard-fojta-b3286879/" target="_blank">https://www.linkedin.com/in/richard-fojta-b3286879/</a></p> <p>Bonusová část: <a href="https://www.pickey.cz/jurij_starynec">https://www.pickey.cz/jurij_starynec</a></p>
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at [email protected] for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.